GAA16CA442

NTSB accident investigation · Cessna 172 · Anchorage, AK · August 20, 2016

Accident · No injuriesData collectionFinal report
Date
August 20, 2016, 12:00 local (20:00 UTC)
Place
Anchorage, AK
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N35408Cessna 172
Defining event
Taxi: Prop/jet/rotor blast/suction
Weather
Visual (VMC) · Day
Status
Completed · report December 5, 2016
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
FAA report
20160820022919A
Case key
93873

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The facility's designation of the taxiway for use by maintenance personnel to conduct high thrust tests without appropriate safeguards in place, which led to maintenance personnel conducting high-power, run-up thrust procedures across the active taxiway and resulted in the loss of directional control of a light, single-engine airplane on the taxiway when it encountered a sudden, unexpected blast of engine thrust.

Findings · 2

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: directional controlAircraft › Aircraft oper/perf/capability · Attain/maintain not possibleCessna 172R: 37 casesAll aircraft: 3,958 casesProbable cause
Design: policy/procedure developmentOrganizational issues › Development · AirportCessna 172R: 1 caseAll aircraft: 17 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The flight instructor of a light single-engine airplane reported that while he and the student pilot were on a taxiway under air traffic control (ATC) instruction, the airplane encountered prop wash, originating from a larger (four engine) turbine-powered airplane performing a maintenance engine(s) run-up. The maintenance run-up was performed in a location adjacent to the active taxiway that was authorized for parking as well as 80% engine(s) power run-ups. The larger turbine-powered airplane was the third in a row a five, of like model airplanes being parked at the location. The light single-engine airplane was not on frequency when the larger turbine-powered airplane was given the clearance, and was not told by ATC at any time during their taxi of the larger turbine-powered airplane's intentions. Subsequently, the light single-engine airplane was blown approximately 80 feet from its original location while taxing behind the larger turbine-powered airplane, which resulted in substantial damage to the firewall. The flight instructor reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. As a safety recommendation the flight instructor stated that the incident could have been prevented with better communications between the tower controllers and the larger turbine-powered airplane's ground personnel.

Factual narrative

The flight instructor of a light single-engine airplane reported that while he and the student pilot were on a taxiway under air traffic control (ATC) instruction, the airplane encountered prop wash, originating from a larger (four engine) turbine-powered airplane performing a maintenance engine(s) run-up. The maintenance run-up was performed in a location adjacent to the active taxiway that was authorized for parking as well as 80% engine(s) power run-ups. The larger turbine-powered airplane was the third in a row a five, of like model airplanes being parked at the location. The light single-engine airplane was not on frequency when the larger turbine-powered airplane was given the clearance, and was not told by ATC at any time during their taxi of the larger turbine-powered airplane's intentions. Subsequently, the light single-engine airplane was blown approximately 80 feet from its original location while taxing behind the larger turbine-powered airplane, which resulted in substantial damage to the firewall. The flight instructor reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. As a safety recommendation the flight instructor stated that the incident could have been prevented with better communications between the tower controllers and the larger turbine-powered airplane's ground personnel.

Aircraft

Registration
N35408
Reported as
Cessna 172 (R)
Category
Airplane
Serial number
17281081
Built
2001
Airframe hours
5,047.8
Engine
Lycoming IO-360-L2A, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · June 24, 2016
Departed
EDF · Anchorage, AK
Destination
EDF · Anchorage, AK
Flight plan
Military VFR
Airport
EDF · Elmendorf Afb
Equipment
None

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Flight instructor
Age
60
Injuries
None
Certificate
Flight instructor
Airplane ratings
Single-engine sea, Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
July 20, 2016
Seat
Right
Flight hours
9,154 total · 2,000 in this make and model · 3,230 as pilot in command · 100 in the last 90 days · 25 in the last 30 days · 4 in the last 24 hours
Role
Student pilot
Age
27
Injuries
None
Certificate
Student
Medical
Class 3, Without waivers/limitations
Seat
Left
Flight hours
12 total · 12 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
4,000 ft overcast
Temperature
61 °F, dew point 54 °F
Altimeter
30.04 inHg
Observed at
PAED

Docket · 2

The files NTSB released with the investigation on October 12, 2016, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.1 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N35408 · 1

Matched to the same aircraft by N-number and date.