Cessna 172H N1408F incident near Tucson, Arizona

Feb 22, 2009 · NTSB number WPR09IA128 · Final report

Probable cause

The flight instructor’s inadequate situational awareness while taxiing that led to an encounter with jet blast.

NTSB analysis

Following an uneventful landing, the student pilot and flight instructor were cleared to taxi the Cessna 172H to the ramp. While taxiing on a taxiway, parallel to an active runway, the flight instructor and student pilot observed a McDonnell Douglas MD-80 transport category airplane holding short of the runway. As the Cessna 172H neared the MD-80's position, the student pilot applied aileron control inputs for possible jet blast and deviated away from the MD-80, towards the inner ramp area. The flight instructor advised the student pilot to stop the airplane due to the MD-80 being positioned "farther back from the hold short line of 11L than initially thought and the presence of a Boeing 757 parked in the inner ramp area." As the Cessna 172H slowed to a stop, the MD-80 "increased engine thrust" to taxi onto the runway. Subsequently, the MD-80’s jet blast tipped the Cessna 172H over onto its right wing, which resulted in minor damage to the outboard wingtip. The tower controller reported that he began to clear the MD-80 for takeoff as he scanned the active runway to ensure all crossing aircraft were clear. The controller then "looked back” and saw the Cessna 172H taxiing behind the MD-80. The controller stated that he stopped issuing the takeoff clearance, however the MD-80 had already powered up.

Text from the NTSB. Open the NTSB docket for WPR09IA128 for the full record.

Event

Date
Feb 22, 2009
Type
Incident
Place
Tucson, Arizona
Nearest airport
Tucson International Airport (TUS)
Highest injury
None
Weather
Visual (VMC)
Light
Day

Cessna 172H

N-number
N1408F
Category
Airplane
Damage
Minor
Operating rule
Part 91 (general aviation)
Purpose of flight
Instructional

From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.