28 Mar 2018: STANLEY Lancair IV-P

28 Mar 2018: STANLEY Lancair IV-P — Unknown operator

No fatalities • Sebring, FL, United States

Probable cause

The failure of ground personnel to obtain permission from airport management to conduct engine test runs; adequately monitor the area behind the B737 for traffic; and install barricades to prevent access behind the running airplane, which resulted in the accident pilot's loss of control during taxi due to an encounter with the jet blast. Contributing to the accident were the accident pilot's failure to detect that the B737 engines were running, and the airport management's failure to establish written standard operating procedures regarding engine runs.

— NTSB Determination

Accident narrative

On March 28, 2018, about 0830 eastern daylight time, an experimental Lancair IV-P, Canadian registration C-GSQQ, was substantially damaged when it was involved in an accident near Sebring, Florida. The private pilot and two passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. While inbound for landing, the pilot made multiple position reports on the airport's published common traffic advisory frequency (CTAF). He landed uneventfully on runway 01 after completing a GPS approach, exited the runway onto taxiway A4, and stopped. He reconfigured the airplane, performed the taxi checks, and noticed a Boeing 737 (B737) south of his position, facing south on a taxiway that paralleled the runway. He thought that the airplane was parked, and neither he nor the right front seat passenger recalled seeing any people on the ground around the B737. He noticed that the left engine cowling was missing, but he could not perceive whether either engine was running, adding that there were no barricades to block the taxiway. The pilot began taxiing westbound about 200 to 300 ft behind the B737 with no aileron control input applied, when the left wing suddenly rose, and the right wing contacted the taxiway. The airplane cartwheeled and came to rest upright on grass at the north edge of the taxiway with the nose landing gear fork and wheel assembly separated. He reported that the empennage was cracked and that there was damage to both wings at their roots, consistent with up-and-down flexing. Maintenance personnel onboard the B737 reported that they were in contact with personnel in two vehicles on the ground near the nose landing gear, but that they were not monitoring the CTAF. Both engines of the B737 were stabilized at 85% power while the individual in one vehicle had a portable radio transceiver and was monitoring the CTAF. That individual reported seeing the accident airplane when it first turned off the runway and crossed the hold short line. He attempted to communicate with the accident pilot on the CTAF, but his transmission was stepped on by another pilot, who was airborne and also attempting to warn the pilot that the B737's engines were running. He then began driving toward the accident airplane, but when it had encountered the jet blast, he broadcast to the B737 cockpit to secure the engines, then went to the accident airplane to render assistance. At the time of the accident, the B737 was positioned at the "north spot," one of its two pre-approved engine run locations on the airport. The executive director of the airport reported that there was an unwritten policy requiring his direct approval for maintenance engine runs for the B737. Personnel involved in the engine runs reported that airport personnel gave such approval; however, the director reported that neither he nor any airport staff gave approval for engine runs that day.

Contributing factors

  • cause Attain/maintain not possible
  • factor Pilot
  • cause Maintenance personnel
  • cause Maintenance provider
  • factor Airport

Conditions

Weather
VMC, wind 100/03kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.