CEN11LA361 · Flournoy Martin R FLOURNOY MR S1S
Matt Tanner Aviation Flournoy Martin R FLOURNOY MR S1S · Accident: landing gear collapse
From Meadow Lake Airport (KFLY) to Meadow Lake Airport (KFLY)
Event
- NTSB case
- CEN11LA361
- 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
Flournoy Martin R FLOURNOY MR S1S
- Aircraft type
- Flournoy Martin FLOURNOY MR S1S
- 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
- N457CF
- Operator
- Matt Tanner Aviation
- Onboard fatalities
- Unknown
- Route
- From Meadow Lake Airport (KFLY), Colorado Springs, COTo Meadow Lake Airport (KFLY), Colorado Springs, CO
- 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
- Landing gear collapse
- 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
- Not determined › Not determined
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 he made a normal touchdown, but during the rollout the airplane began to yaw to the left. He attempted to correct his loss of directional control by applying full right rudder and right brake. Despite his efforts to straighten the airplane's path, the airplane began to bounce/skip to the side and subsequently ground looped. During the impact sequence, the lower right wing tip, aileron and aft section of the fuselage sustained substantial damage. Postaccident examination of the airplane revealed that the tailwheel spring attach bolt had pulled through the fuselage structure where it was mounted. The bolt was intact and there was no obvious damage to the threads. It could not be determined why the bolt separated prior to the accident.
Probable cause
The pilot’s loss of directional control during the landing rollout due to failure of the tailwheel assembly for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11LA361
- Event ID
- 20110531X95659
- Case number
- CEN11LA361
- 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: c60acceb886cc07e1826ad1e71d092e5e4f09ffdb37e862c5be3089514537e99; retrieved 2026-09-15T16:13:48.183Z.