Rick said: > The ideal, but probably unobtainable, result would be a excerpt > from the accident investigation report: > > 'The aircraft impacted nose down with an angle of approximately > 83 degrees to the vertical and 3 degrees of bank. There was no > evidence of rotation about any of the aircraft axes. The > airspeed was approximately 250 knots. The state of the spinner, > recovered portions of airscrew, and engine crankshaft suggest > that the engine was at flight idle with the blades feathered. > > Upon impact the engine rotated about the lower rear mounts, > breaking through the firewall as it did so. Whilst it later > detached from these mounts it initially rotated through > approximately 130 degrees, reducing the occupancy space in the > area of the forward seats as it did so. This is consistent with > the severe trauma to the lower limbs and chest suffered by the > pilot...'
That doesn't seem too hard. Curt, how about having FGFS write the values of all the properties to a file in a shellscript acceptable fashion ? Given a collection of such files, with names that describe the developers' opinion on survivability, it should be easy (and fun) to generate a scripted message. Once we have it working, we either move the script execution into FGFS or use "popen()" to call the script and then format the results onto the screen. The NTSB reports follow a pattern laid down by regulation, which is why it wouldn't be too difficult to code up. Given a basic version that mostly works, I suspect the real investigators would offer comments and suggestions. > Or maybe just a balance sheet: > > Replacement Aircraft: X > Litigation (Surviving Passengers and Relatives of > non-survivors): Y > Funeral Costs: Z > Lost revenue: P > Increased insurance premiums: Q That one is alot easier; the numbers are fairly static. However, most users won't be interested in boring facts so it doesn't meet the underlying entertainment goal. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
