> OTOH getting beyond something fairly simple would probably need
> some sort of time history of key events and some aero data.
Ok, here's one as example. It's the second plane I trained in, after the
first one was intentionally flown acrobatically until the wings failed.
This accident wasn't me ... it had already left the club I'm in by then.
http://www.ntsb.gov/ntsb/brief.asp?ev_id=20010227X00520&key=1
NTSB Identification: LAX01LA102.
The docket is stored in the (offline) NTSB Imaging System.
Accident occurred Thursday, February 15, 2001 at San Diego, CA
Aircraft:Cessna 172N, registration: N4922D
Injuries: 2 Uninjured.
[ all of that is trivial ]
During landing rollout, the airplane veered off the runway
and collided with obstacles.
[ should be easy to recognize, based on position-relative-to-runway data ]
At the completion of a 3.7-hour-long flight,
[ data trivially available ]
the
tower controller advised the pilot that the local wind was from 270 degrees
at 6 knots, and asked him to switch runways to the parallel.
[ we don't have that feature yet ]
After touchdown, the airplane was still traveling about 50 knots when,
approaching runway 28L's midfield location, the pilot lost
directional control.
[ aka heading became significantly different from runway direction, at speed ]
The left wing rose upward. The airplane veered off the runway
and impacted a sign. Airport personnel reported that
the collision occurred about 1,000 feet upwind of the runway's threshold.
[ when we get airport signage into the scenery. More to the point, when
someone create a tool, so I can add the signs to KMYF myself ]
The airplane came to a stop about 550 feet farther upwind of
the sign and about 200 feet north of the runway.
[ also easy to do, albeit with different wording ]
No mechanical malfunctions were reported with the airplane.
[ we don't have a malf feature, but even if we did, this is easy ]
The National Transportation Safety Board determines
the probable cause(s) of this accident as follows.
[ we'd need to use different words here, to avoid getting in trouble ]
The pilot's failure to maintain directional control
of the airplane during landing rollout.
[ hrmph ]
Full narrative available
[ I merged it on for this message ]
On February 15, 2001, about 1516 hours Pacific standard time,
a Cessna 172N, N4922D, veered off the runway and collided with a
taxiway sign during landing rollout on runway 28L
at the Montgomery Field, San Diego, California.
[ All of that should be trivial to derive from the simulator state ]
The airplane was substantially damaged.
Neither the airline transport certificated pilot nor passenger was injured.
[ comment based on decelerations from FDM ]
Plus One Flyers, Inc., San Diego, operated the airplane.
[ I have no idea what we'd put for that, grin ]
Visual meteorological conditions prevailed,
and an instrument flight rules flight plan was filed.
[ The former is trivial from the weather; the latter is hard to do for now ]
The personal flight was performed under 14 CFR Part 91,
and originated in Scottsdale, Arizona, about 1235 mountain standard time.
[ Boilerplate, and the latter should be known by the simulator ]
Airport personnel reported that the collision occurred about 1,000 feet
upwind of the runway's threshold. The airplane impacted the
taxiway "C" sign and veered off the runway.
[ All of that should be derived from the collision transient with
the object description from the scenery database. ]
The airplane came
to a stop about 550 feet farther upwind of the sign and about 200 feet
north of the runway.
[ Relative position of wreckage to first collision impact recorded ]
The pilot stated to the National Transportation Safety Board investigator
that during the landing rollout, as the airplane was
decelerating through about 50 knots, the left wing suddenly lifted up.
Thereafter, he lost control of the airplane. He additionally
reported that he was unaware of the reason for this occurrence.
[ The user has to write this bit within 1 minute of the crash ]
No mechanical malfunctions were reported with the airplane.
[ simulator malf database report ]
In the pilot's partially completed accident report,
he indicated that when the airplane was "almost half way down the runway"
the left wing rose up, and thereafter he lost control of the airplane as
it "violently" veered off the runway. The pilot also reported that when he
was on final approach the tower controller reported that the wind was from
270 degrees at 6 knots.
[ This bit is written after more thought ... and talking to insurance ]
[ ... that's all there is to most accident reports ]
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
