WPR26LA018 · Cessna 180 H
Cessna 180 H · Accident: nose over/nose down during takeoff
Event
- NTSB case
- WPR26LA018
- 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
- Event fatalities
- Unknown
- 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 H
- 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
- N249MD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 60 years (built 1965)
- 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 · rejected 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
- Nose over/nose down
- 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 systems
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was departing from a down-sloping runway surrounded by terrain that permitted departures only in one direction. He estimated there was a 12-knot tailwind. During the takeoff roll, as the airplane neared the end of the runway the pilot decided to abort the takeoff. The pilot applied and maintained braking input as the airplane briefly became airborne. The airplane touched back down, nosed over, and came to rest inverted on the runway. During the accident sequence, the airplane incurred damage to both wings. The pilot reported that there were no pre-impact mechanical malfunctions or failures that would have precluded normal operation of the airplane.
Probable cause
The pilot’s continued application of brakes during an aborted takeoff in a tailwind on down-sloping terrain, which resulted in a nose-over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR26LA018
- Event ID
- 20251014201848
- Case number
- WPR26LA018
- 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, coordinates, cause areas. 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: a36a050dac8256cf988260a3841b4de8c6f236d3683a6026eb4cc41f7a050263; retrieved 2026-09-16T20:28:02.337Z.