FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA071 · Cessna 150F

4 Jan 2025 · McKinney, TX, United States

Texins Flying Club Cessna 150F · Accident: abnormal runway contact during landing

From McKinney National Airport (TKI) to McKinney National Airport (TKI)

Report a problem

Event

NTSB case
CEN25LA071
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
Event fatalities
Unknown
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 150F

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
N3589L
Onboard fatalities
Unknown
Route
From McKinney National Airport (TKI), McKinney, TXTo McKinney National Airport (TKI), McKinney, TX
Aircraft age
About 60 years (built 1965)
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 · flare/touchdown
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
Abnormal runway contact
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 oper/perf/capability
  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot and flight instructor were practicing touch-and-go landings with a left crosswind of about 5 knots. The student pilot reported that the airplane began to drift right during the landing flare. As he corrected for the right drift, the airplane pitched nose down and landed on the nose landing gear. The nose landing gear then collapsed, and the airplane slid to a stop on the runway in a nose down attitude. Several engine mount tubes fractured when the nose landing gear collapsed aft. The student pilot reported that he did not maintain a proper landing flare while he corrected for the right drift.

Probable cause

The flight instructor’s inadequate supervision and delayed remedial action and the student pilot’s failure to maintain a proper landing flare, which resulted in a nose down impact with the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA071
Event ID
20250107199519
Case number
CEN25LA071
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, cause areas. 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: 84215889d45a6b3a6a0f38c8ed2a2d02a853ab7bf784bf27f699cbc7cef8301b; retrieved 2026-09-16T19:35:13.759Z.