FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16LA225 · Piper PA 28-236

17 Jun 2016 · Punta Gorda, FL, United States

Piper PA 28-236 · Accident: loss of control on ground during landing

From Peter O Knight Airport (TPF) to Punta Gorda Airport (PGD)

Report a problem

Event

NTSB case
ERA16LA225
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA 28-236

Aircraft type
Piper PA-28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N8161X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Peter O Knight Airport (TPF), Tampa, FLTo Punta Gorda Airport (PGD), Punta Gorda, FL
Aircraft age
About 36 years (built 1980)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control on ground
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Operating environment
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot stated that, during the landing roll, the airplane suddenly departed the left side of the 150-ft-wide runway into the grass, resulting in substantial damage to the left wing. The pilot initially thought a tire had blown, but when he exited the airplane, he noticed a McDonnell-Douglas MD-83 parked on the movement area of the adjacent taxiway performing a maintenance test run of its engines and realized he had been blown off the runway.

Before the accident, the tower controller had cleared the MD-83 to position itself in the movement area adjacent to the landing runway; the positioning resulted in the engine and resultant exhaust being directed toward the landing area of the runway. The controllers did not warn the accident pilot about the MD-83 and its purpose on the taxiway, as required per FAA policy. Additionally, the local procedures for positioning transport category airplanes to do engine test runs was not formally documented, and the informal procedure in use at the time of the accident did not adequately protect aircraft operating on the airport from jet blast. The estimated idle jet engine exhaust velocity of the MD-83 was 35 knots. Combined with the prevailing wind, the estimated sudden right quartering headwind acting on the accident airplane would have been about 39 knots. As a result of this investigation, the air traffic control tower and airport authority developed and disseminated procedures for conducting high-power engine test runs in the movement area of the airport.

Probable cause

The tower controller’s failure to identify and mitigate jet blast from an airplane conducting an engine test run, and the effect of the jet blast on landing traffic, which resulted in a runway excursion when a landing airplane encountered the blast. Contributing to the accident was the lack of procedures for positioning high-powered airplanes conducting engine test runs in the airport movement area.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16LA225
Event ID
20160621X34119
Case number
ERA16LA225
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 587793d0e7fd927bf4b66129aa557beccd819a5668102f98607bf246a23ca682; retrieved 2026-09-16T03:32:04.405Z.