Regulations and Government
FAA still not policing Pt 91 management cos
This month marks the six-year anniversary of one of the most ­infamous accidents in the history of business aviation–the crash of a chartered Challenger
The Challenger 600 that crashed on takeoff from Teterboro Airport in 2005 was carrying too much fuel and its c.g. was too far forward. The flight, operating under Part 91, was virtually free of FAA oversight, as it would still be today–a recipe for another disaster.
The Challenger 600 that crashed on takeoff from Teterboro Airport in 2005 was carrying too much fuel and its c.g. was too far forward. The flight, operating under Part 91, was virtually free of FAA oversight, as it would still be today–a recipe for another disaster.

This month marks the six-year anniversary of one of the most ­infamous accidents in the history of business aviation–the crash of a chartered Challenger 600 at Teterboro Airport. Six years later, has the FAA incorporated the lessons learned into its regulations?

There is an irony apparent in the events following the February 2005 Challenger accident at Teterboro. Investigators nearly ignored the primary cause of the crash, as the NTSB focused primarily on 14 CFR Part 135 operational control issues and the lack of FAA oversight as the secondary causes. The industry and the media then homed in on the FAA's efforts to tighten the reins of operational control for 14 CFR Part 135 operators and the aircraft on their certificates.