OpenAirDocs.org

20190918018179I

Incident · Minor damage
Open the Markdown

FAA incident report · Cessna 172E · South Burlingto, VT · September 18, 2019

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
September 18, 2019 · 13:30 local
Place
South Burlingto, VT
Airport
Burlington International
Phase of flight
Taxi
Operating rules
General operating rules (Part 91)
Damage
Minor damage
Aircraft
N5604T
Reported as
Cessna 172E
Reported engine
Continental 0-300 series
People aboard
2
Fatal injuries
0
Other injuries
0
N5604TRegistered now · Cessna 172ES/N 17251504 · Built 1964Airframe modelCessna 172EEngine modelContinental 0-300 seriesReciprocating

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

As reported in air traffic mandatory occurrence report BTV-M-2019/09/18-0002: EDV5103(endeavor crj) established communication with ground control controller ready to taxi and requested a place they could run the engines a little higher to burn fuel. The controller instructed EDV5103 to taxi to runway 33 at taxiway c and advised them to burn off fuel at taxiway c. N56O4T (incident aircraft) established communication with controller ready to taxi and was instructed to taxi to runway 33 via taxiways c, k, and j. the controller made two attempts to establish communications with EDV5103 to determine if they were still above idle speed and received no reply. The controller instructed incident aircraft to turn left on taxiway k and j to runway 33 and hold short of runway 33 at taxiway j. incident aircraft advised controller that "something happened" to the aircraft and that they would need to be towed.

Jet blast from EDV5103 caused incident aircraft to become unstable and resulted in the right wing tip and propeller to contact ground. Evidence at this time has damage limited to the right wing tip and propeller.

As the FAA filed it

AS REPORTED IN AIR TRAFFIC MANDATORY OCCURRENCE REPORT BTV-M-2019/09/18-0002: EDV5103(ENDEAVOR CRJ) ESTABLISHED COMMUNICATION WITH GROUND CONTROL CONTROLLER READY TO TAXI AND REQUESTED A PLACE THEY COULD RUN THE ENGINES A LITTLE HIGHER TO BURN FUEL. THE CONTROLLER INSTRUCTED EDV5103 TO TAXI TO RUNWAY 33 AT TAXIWAY C AND ADVISED THEM TO BURN OFF FUEL AT TAXIWAY C. N56O4T (INCIDENT AIRCRAFT) ESTABLISHED COMMUNICATION WITH CONTROLLER READY TO TAXI AND WAS INSTRUCTED TO TAXI TO RUNWAY 33 VIA TAXIWAYS C, K, AND J. THE CONTROLLER MADE TWO ATTEMPTS TO ESTABLISH COMMUNICATIONS WITH EDV5103 TO DETERMINE IF THEY WERE STILL ABOVE IDLE SPEED AND RECEIVED NO REPLY. THE CONTROLLER INSTRUCTED INCIDENT AIRCRAFT TO TURN LEFT ON TAXIWAY K AND J TO RUNWAY 33 AND HOLD SHORT OF RUNWAY 33 AT TAXIWAY J. INCIDENT AIRCRAFT ADVISED CONTROLLER THAT "SOMETHING HAPPENED" TO THE AIRCRAFT AND THAT THEY WOULD NEED TO BE TOWED.

JET BLAST FROM EDV5103 CAUSED INCIDENT AIRCRAFT TO BECOME UNSTABLE AND RESULTED IN THE RIGHT WING TIP AND PROPELLER TO CONTACT GROUND. EVIDENCE AT THIS TIME HAS DAMAGE LIMITED TO THE RIGHT WING TIP AND PROPELLER.