1705
FlightFinder has no observed route profile for this registration. The documented safety events below are available independently of live flight tracking.
Safety history
- October 29, 2009Accident
USAF and US authorities concluded that no single factor or individual act or omission was the cause of the collision. Investigations concluded that it was the consequence of a tragic confluence of events, missed opportunities, and procedure/policy issues in an airspace where most aircraft fly under a "see-and-avoid" regime. Full accident record