FTW95LA155 · Cessna 152
Cessna 152 · Accident: loss of control in flight during initial climb
From an unrecorded airport to 1F9 · Bridgeport, TX
Event
- NTSB case
- FTW95LA155
- 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 152
- Aircraft type
- Cessna 152
- 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
- N5426B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 1F9 · Bridgeport, TX
- 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; Tree(s)
- 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 › Airspeed(vlof), not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE STUDENT PILOT LOST TRACK OF TIME AND IT WAS DARK WHEN HE DECIDED TO TAKE OFF TO RETURN TO HIS HOME BASE. ALTHOUGH HE WAS NOT ENDORSED FOR NIGHT FLIGHT, HE WAS CONCERNED HIS FLIGHT INSTRUCTOR AND THE SCHOOL PRESIDENT WOULD BE ANGRY WITH HIM. THE PILOT FOLLOWED 'GREEN LIGHTS' AND INADVERTENTLY MADE A SHORT-FIELD TAKEOFF FROM A 900-FOOT TAXIWAY. ACCORDING TO PILOT, THE NOSE PITCHED UP AND THE AIRPLANE STALLED. THE PILOT LOWERED THE NOSE TO RECOVER, BUT WAS FORCED TO RAISE THE NOSE AGAIN BECAUSE OF TREES AHEAD. THE AIRPLANE 'STALLED AGAIN' AND COLLIDED WITH TREES. DURING AN FAA INTERVIEW, THE PILOT REPORTED THAT THE LANDING LIGHT WAS INOPERATIVE AND HE TAXIED TO THE RUNWAY WITH THE GREEN LIGHTS.
Probable cause
THE PILOT'S FAILURE TO ATTAIN PROPER LIFT-OFF SPEED RESULTING IN AN INADVERTENT STALL. FACTORS WERE THE SELECTION OF THE TAXIWAY FOR TAKE-OFF AND THE INOPERATIVE LANDING LIGHT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW95LA155
- Event ID
- 20001207X03130
- Case number
- FTW95LA155
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1995-04-01.
- API snapshot SHA-256: 8e0c8cd8dd79c0795b375f25ca3edf99bb1fb7e4b65a177c4da2bb27a706a0a7; retrieved 2026-09-21T22:21:37.496Z.