FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16CA128 · Cessna 180 J

13 Mar 2016 · South Burlington, VT, United States

Cessna 180 J · Accident: loss of control on ground during takeoff

From Patrick Leahy Burlington International Airport (BTV) to Underhill, VT (private airstrip)

Report a problem

Event

NTSB case
ERA16CA128
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

Cessna 180 J

Aircraft type
Cessna 180
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
N9925N
Onboard fatalities
Unknown
Route
From Patrick Leahy Burlington International Airport (BTV), South Burlington, VTTo Underhill, VT (private airstrip)
Aircraft age
About 41 years (built 1975)
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
Takeoff
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
  • Personnel issues › Task performance

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

NTSB narrative

The pilot of the tailwheel-equipped airplane reported that during takeoff roll the airplane encountered a gust of wind from the left side. He said that he "dipped" the left wing in an attempt to counter the wind gust but lost control of the airplane, flipped over nose first and impacted the runway. The airplane sustained substantial damage to the vertical stabilizer.

The pilot reported no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Probable cause

The pilot's failure to maintain airplane control during takeoff roll, which resulted in a nose over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16CA128
Event ID
20160314X84212
Case number
ERA16CA128
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: aa777e436d9b241989033cd09fd6203c99e6a52560368843c6519e48df96ad9b; retrieved 2026-09-16T03:13:08.586Z.