FTW02LA174 · Cessna 150
Cessna 150 · Accident: partial loss of engine power (mechanical failure) during initial climb
From Hicks Air Field (T67) to an unrecorded destination
Event
- NTSB case
- FTW02LA174
- 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 150
- Aircraft type
- Cessna 150
- 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
- N6249R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hicks Air Field (T67), Forth Worth, TXTo not recorded
- 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
- Initial climb
- 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
- Partial loss of engine power (mechanical failure)
- 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
- Mixture control › Disconnected
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane had just taken off and was climbing out when the engine started to lose rpm. The airplane continued to climb straight for a couple of hundred feet, then the pilot turned the airplane crosswind hoping to make it around the pattern and land. When the aircraft turned downwind it wasn't climbing, prompting the pilot to make a forced landing in a field. The airplane touched down, impacted a berm, bounced, then impacted the terrain a second time before coming to rest in an upright position. An examination by an FAA inspector revealed the mixture control rod was separated from the carburetor.
Probable cause
the partial loss of engine power due to the mixture control rod separating from the carburetor. A contributing factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW02LA174
- Event ID
- 20020611X00847
- Case number
- FTW02LA174
- 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: 52d56c802c737e2203c56fad5d0da0ec271df8b9f240be4caefe63c6ba45a2a2; retrieved 2026-09-22T10:52:13.302Z.