# NTSB WPR09IA128: Cessna 172H, N1408F, Tucson, AZ, February 22, 2009

- Type: NTSB incident investigation
- Classification: Incident · No injuries · Incident investigation · Final report
- Date: February 22, 2009, 14:57 local (21:57 UTC)
- Place: Tucson, AZ
- Coordinates: 32.115833, -110.940834 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=32.1158&lon=-110.9408&mi=10
- Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping)
- Defining event: [Taxi: Prop/jet/rotor blast/suction](https://openairdocs.org/ntsb-events/082)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report November 9, 2009
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 73383
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR09IA128
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73383/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=73383
- Page: https://openairdocs.org/ntsb/WPR09IA128

## Probable cause

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

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Perception/orientation/illusion: situational awareness](https://openairdocs.org/ntsb-findings/02022035): Personnel issues › Psychological · Instructor/check pilot (probable cause); cases with it: [Cessna 172H, 1 case](https://openairdocs.org/ntsb-findings/02022035/cases.md?model=2072424), [All aircraft, 111 cases](https://openairdocs.org/ntsb-findings/02022035/cases.md)
- [Turbulence: wake turbulence](https://openairdocs.org/ntsb-findings/03032025): Environmental issues › Conditions/weather/phenomena · Effect on equipment (probable cause); cases with it: [Cessna 172H, 1 case](https://openairdocs.org/ntsb-findings/03032025/cases.md?model=2072424), [All aircraft, 47 cases](https://openairdocs.org/ntsb-findings/03032025/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Taxi: Prop/jet/rotor blast/suction](https://openairdocs.org/ntsb-events/082) (defining event); cases with it: [Cessna 172H, 1 case](https://openairdocs.org/ntsb-events/082/sequence.md?model=2072424), [All aircraft, 44 cases](https://openairdocs.org/ntsb-events/082/sequence.md)
- [Taxi: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna 172H, 10 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072424), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Taxi: Roll over](https://openairdocs.org/ntsb-events/097); cases with it: [Cessna 172H, 1 case](https://openairdocs.org/ntsb-events/097/sequence.md?model=2072424), [All aircraft, 261 cases](https://openairdocs.org/ntsb-events/097/sequence.md)

## 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.

## Factual narrative

On February 22, 2009, about 1457 mountain standard time, a Cessna 172H, N1408F, sustained minor damage while taxiing at the Tucson International Airport (TUS), Tucson, Arizona. The airplane was registered to Zuluft LLC and operated by Sonoran Wings, Tucson, under the provisions of Title 14 Code of Federal Regulations Part 91. The student pilot and flight instructor were not injured. Visual meteorological conditions prevailed and no flight plan was filed for the instructional flight. The local flight originated from TUS about 1400. In a written statement, the operator reported that after the flight instructor and student pilot landed on runway 11R, they exited onto taxiway Alpha 11. The tower controller cleared the flight to cross runway 11L and contact the ground controller once clear of the runway. After crossing runway 11L, the flight instructor and student pilot switched to the ground control frequency and obtained clearance to taxi to the ramp via taxiway Alpha and taxiway Delta. While taxiing, the student pilot and instructor observed an American Airlines McDonnell Douglas MD-80 airplane holding short of runway 11L at taxiway Alpha 4. The operator stated that the student pilot applied aileron control inputs for possible jet blast and deviated away from the MD-80, towards the inner ramp area. The operator further reported that 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 student pilot and flight instructor slowed the airplane to a stop, the MD-80 "increased engine thrust" to taxi onto the runway. Subsequently, the airplane tipped over onto its right wing. In a written statement, the tower controller reported that he began to clear American Airlines flight 1418 (AAL1418) for takeoff as he scanned the runway to insure all crossing aircraft were clear of the active runway. The controller "looked back and saw a Cessna taxiing behind AAL1418." The controller stated that he stopped issuing the takeoff clearance for the MD-80, however they had already powered up. The ground controller reported that he taxied the Cessna 172H to Sonoran Wings via taxiway Alpha and taxiway Delta. At taxiway alpha four, "AAL1418 powered up for departure." Examination of the airplane by the operator revealed that the outboard tip of the right wing sustained minor damage. Federal Aviation Administration (FAA) Order JO 7110.65S, Air Traffic Control, specifies procedures and practices to be used by air traffic control personnel. Section 2-1-20 (b) advises controllers to "Issue cautionary information to any aircraft if in your opinion, wake turbulence may have an adverse effect on it." Section 2-1-20 (note) specifies that "Although not mandatory during ground operations, controllers may use the words jet blast, propwash, or rotorwash, in lieu of wake turbulence, when issuing acautionary advisory."

## Aircraft

- Registration: [N1408F](https://openairdocs.org/deregistered/N1408F-2018-06-26), registration cancelled 2018-06-26, S/N 17254903, built 1966 (OpenAirDocs)
- Reported make and model: CESSNA 172H
- Registry model: [Cessna 172H](https://openairdocs.org/model/cessna-172h) (registry code 2072424) (OpenAirDocs)
- Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17254903
- Airframe hours: 5759
- Engines: CONT MOTOR O-300 SER 145 horsepower reciprocating
- Damage: Minor damage
- Flight: Instructional, Part 91
- Operator: Sonoran Wings
- Registered owner: Zuluft LLC
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, November 10, 2008, 88 hours before
- Departed: TUS, Tucson, AZ
- Destination: TUS, Tucson, AZ
- Flight plan: Unknown
- Airport: TUS, Tucson International Airport

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Flight instructor; age 25; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, without waivers/limitations; last flight review November 6, 2008; seat: right; flight hours: 1,020 total, 816 in this make and model, 952 as pilot in command, 107 in the last 90 days, 40 in the last 30 days, 3 in the last 24 hours
- Student pilot; age 19; injuries: none; student; medical: class 3, unknown; seat: left; flight hours: 44 total, 35 in this make and model, 1 as pilot in command, 22 in the last 90 days, 9 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 20° at 5 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 82 °F, dew point 7 °F
- Altimeter: 30.13 inHg
- Observed at: TUS

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Incident 20090222003139I](https://openairdocs.org/incident/20090222003139I), Feb 22, 2009: Cessna 172H, Tucson, AZ, Minor damage. (-23) While taxiing to parking after landing, the Cessna 172 taxied behind an MD80 as it was powering up to take the active runway. The MD80 blew the Cessna…

## Docket (3 files)

The files NTSB released with the investigation on September 14, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=73383. 880 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 536 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40316883&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF
- Air Traffic Controller Statements (item 2, .PDF, 141 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40316884&FileExtension=.PDF&FileName=Air%20Traffic%20Controller%20Statements-Redacted.PDF
- Airport Diagram (item 3, .PDF, 203 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40316885&FileExtension=.PDF&FileName=Airport%20Diagram-Master.PDF

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.