The pilot saw “three dark flashes” flit in front of his F-16 fighter
as he pulled up following a touch-and-go landing during a training
flight last June 26 in Arizona. An acrid smell and buzzing instantly
filled Radon 11’s cockpit. Then came a “pop” from the plane’s engine, followed by a “bang.” A pilot aboard Honker 11, a second F-16 4,000 feet behind Radon 11,
saw an orange flame and sparks spitting from its engine. “Tower, Radon
11, emergency,” the first pilot radioed Luke Air Force Base. “We’ve got a
bird strike…engine’s about to stall.”
Nothing concentrates a pilot’s mind like running out of sky by losing
power close to the ground. “This created a worst-case emergency for a
single-engine aircraft: low and slow with a questionable ability to
produce thrust,” says the Air Force’s recently-released investigation into the accident.
But although three unidentified small birds triggered the emergency
by flying into the F-16′s engine, the pilot at the controls of Radon 11 caused the ensuing crash, according to the investigation. While we noted earlier this week that bird strikes are a big problem for the Air Force, the crash of Radon 11 makes clear that such avian collisions are not tantamount to a Bail-Out-for-Free card.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment