FTW93LA093 · Cessna 150M
Pegasus Flight Center Cessna 150M · Accident: loss of control in flight during initial climb
From Abilene Regional Airport (ABI) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- FTW93LA093
- 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
- 0
- 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 150M
- 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
- N714AT
- Operator
- Pegasus Flight Center
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Abilene Regional Airport (ABI), Abilene, 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
- 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
- Substantial
Cause areas
- Pilot in command › Stall, inadvertent
Approximate · Estimated position: the centre of Fort Worth, TX, the place the record names. Not the accident site.
NTSB narrative
A STUDENT PILOT ON A SOLO CROSS COUNTRY FLIGHT ATTEMPTED TO TAKEOFF FROM AN AIRPORT NEAR HIS FINAL DESTINATION. DURING THE TAKEOFF THE AIRPLANE WAS OBSERVED ESTABLISHING A HIGH ANGLE OF ATTACK AS IT APPROACHED A FENCE AT THE DEPARTURE END OF THE 3,740 FOOT RUNWAY. AFTER CLEARING THE FENCE, THE PILOT WAS REPORTED TO HAVE RETRACTED THE FLAPS AND THE AIRPLANE STALLED IMPACTING THE GROUND IN A NOSE LOW ATTITUDE. WIND WAS REPORTED BY THE PILOT TO BE FROM 330 DEGREES AT 13 KNOTS, GUSTING TO 25
Probable cause
INADVERTENT STALL. A FACTOR WAS THE TAILWIND
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW93LA093
- Event ID
- 20001211X11976
- Case number
- FTW93LA093
- 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. 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: f3309f15ab83c61fec3b8cbd5f30a1c540440cae33f2a544bc412812953869fa; retrieved 2026-09-21T14:32:30.455Z.