CEN14CA503 · Maule MT 7-260
Maule MT 7-260 · Accident: abnormal runway contact during takeoff
From Lago Vista Texas Rusty Allen Airport (KRYW) to Lago Vista Texas Rusty Allen Airport (KRYW)
Event
- NTSB case
- CEN14CA503
- 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
Maule MT 7-260
- Aircraft type
- Maule MT-7
- 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
- N719WM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lago Vista Texas Rusty Allen Airport (KRYW), Largo Vista, TXTo Lago Vista Texas Rusty Allen Airport (KRYW), Largo Vista, TX
- Aircraft age
- About 8 years (built 2006)
- 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
- Abnormal runway contact
- 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 › Conditions/weather/phenomena
- 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
Prior to departure, the pilot noted the wind from the right at 8-16 knots and gusting 16-21 knots. He added that just after the airplane got airborne, there was a downdraft, and the airplane bounced three times. The airplane then made three larger bounces, before the nose landing gear collapsed and the propeller contacted the runway. The airplane exited the runway and came to rest in the grass. Examination of the airplane revealed substantial damage to the fuselage and left wing. The pilot reported no mechanical anomalies that would have precluded normal operation.
Probable cause
The pilot's inadequate compensation for gusting wind conditions during takeoff, which resulted in the nose landing gear impacting the runway and the subsequent collapse of the nose landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA503
- Event ID
- 20140918X90059
- Case number
- CEN14CA503
- 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: ddee77d50cd98941337df3520c0b5783d7dd061609bccef5c6800fb42803c2d7; retrieved 2026-09-16T01:46:31.263Z.