CEN14LA213 · Crow MUSTANG II
Crow MUSTANG II · Accident: hard landing
From Cochran County Airport (F85) to Cochran County Airport (F85)
Event
- NTSB case
- CEN14LA213
- 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
Crow MUSTANG II
- Aircraft type
- Crow MUSTANG
- 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
- N48MK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cochran County Airport (F85), Morton, TXTo Cochran County Airport (F85), Morton, TX
- Aircraft age
- Built the same year (2014)
- 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 · flare/touchdown
- 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
- Hard landing
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the accident occurred during the third flight test of the recently completed amateur-built airplane. The pilot stated that there were no anomalies with the airplane during his preflight inspection or before-takeoff engine run-up. After an uneventful takeoff, he proceeded to a nearby practice area where he completed basic flight maneuvers and measured cruise performance parameters before returning to the airport for a full-stop landing. Upon returning to the airport, the pilot decided to land on runway 22 because it was longer and wider than the other runway, and the prevailing wind from the south-southwest favored either runway. The airplane landed hard, bounced, and then veered off the left side of the runway before the pilot could regain control. The airplane subsequently nosed over after encountering soft terrain located alongside the runway. Postaccident wreckage examinations revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. A review of available wind data indicated that a gusting left crosswind component of 9 to 14 knots existed during the landing.
Probable cause
The pilot's improper landing flare after encountering a gusting crosswind and his inadequate recovery from the subsequent bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14LA213
- Event ID
- 20140423X14414
- Case number
- CEN14LA213
- 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: 92dc20c91217002efb7566024628e754cd2f730c42b728720a30850ee3cac011; retrieved 2026-09-15T23:32:19.844Z.