WPR13CA097 · Cessna 140
Cessna 140 · Accident: nose over/nose down during landing
From Ryan Field (RYN) to Ryan Field (RYN)
Event
- NTSB case
- WPR13CA097
- 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 140
- Aircraft type
- Cessna 140
- 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
- N223PE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ryan Field (RYN), Tucson, AZTo Ryan Field (RYN), Tucson, AZ
- Aircraft age
- Not recorded
- 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
- 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 oper/perf/capability
- Aircraft › Aircraft systems
- Personnel issues › Task performance
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 returning to the departure airport and completed a normal traffic pattern for the active runway. After touchdown, he attempted to hasten the landing roll and exit off the runway at the first turnoff to accommodate the airplane that was landing after him. The tailwheel and rudder began to shimmy and, in response, the pilot manipulated the control wheel forward. He then applied brake pressure in an attempt to make the exit, and the airplane lurched forward, coming to rest inverted on the runway. The wings, fuselage, and rudder were substantially damaged.
The pilot stated that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. He additionally reported that he thought the accident may have been prevented if he increased his yearly flying time and flew with an instructor more frequently.
Probable cause
The pilot’s failure to maintain directional control during the landing roll and his excessive application of brakes, which resulted in a noseover.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13CA097
- Event ID
- 20130121X03228
- Case number
- WPR13CA097
- 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. 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: 7373fd3076803a2b533baa34c5c68c8e71cfccef3b76a7b0563162673ce73205; retrieved 2026-09-15T20:46:44.797Z.