FTW04LA010 · General Motors FM-2
Commemorative Air Force General Motors FM-2 · Accident: loss of control in flight while maneuvering
From Ellington Airport (EFD) to Ellington Airport (EFD)
Event
- NTSB case
- FTW04LA010
- 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
- 1 · 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
General Motors FM-2
- Aircraft type
- General Motors FM-2
- 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
- N681S
- Operator
- Commemorative Air Force
- Onboard fatalities
- Unknown
- Route
- From Ellington Airport (EFD), Houston, TXTo Ellington Airport (EFD)
- 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
- Maneuvering
- First occurrenceThe 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While maneuvering to land, the pilot inadvertently stalled and impacted the terrain. The pilot had been instructed by air traffic control to increase the separation between it and the airplane it was following. Several witnesses stated the airplane did a series of 360-degree steep turns. During a right turn, the airplane pitched nose up, the wings "wobbled", the airplane descend and entered a partial spin. One witness stated it appeared the airplane, approximately 50 feet agl, attempted to level off; however, then it impacted the terrain in a nose down attitude. Another witness stated the propeller was turning and did not notice any problems with the airplane or engine. The witnesses did not observe any smoke or fire from the airplane prior to the impact.
Probable cause
The pilot's failure to maintain airspeed resulting in an inadvertent stall/spin while maneuvering to land.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW04LA010
- Event ID
- 20031021X01782
- Case number
- FTW04LA010
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 16f4bf8590074f6155b19578f2f015c51f77c0efa5870425779c7b1340e54c29; retrieved 2026-09-20T18:52:47.660Z.