FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA15CA104 · Cessna 150F F

30 May 2015 · Harlingen, TX, United States

Cessna 150F F · Accident: loss of control on ground during landing

From Valley International Airport (HRL) to Valley International Airport (HRL)

Report a problem

Event

NTSB case
GAA15CA104
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 150F F

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
N8126S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Valley International Airport (HRL), Harlingen, TXTo Valley International Airport (HRL), Harlingen, TX
Aircraft age
About 49 years (built 1966)
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 · landing roll
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
Loss of control on ground
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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

According to the student pilot, he was practicing touch and go landings on his fifth solo flight. Two landings were completed on a runway with a direct headwind, but on the third landing air traffic control instructed him to land on an adjacent runway with a crosswind. The student pilot reported that he touched down with an appropriate crosswind technique, but during the landing roll the airplane began swerving to the left and he lost directional control. Subsequently, the nose gear collapsed on the runway and the airplane came to rest upright on its nose and right wing. The reported winds at the airport about the time of the accident were from 110 degrees true at 16 knots, and the runway heading was 170 degrees.

The student pilot reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The airplane sustained substantial damage to the right wing and firewall.

Probable cause

The student pilot's failure to maintain directional control while landing with a crosswind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA15CA104
Event ID
20150603X42135
Case number
GAA15CA104
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. 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: c7ad6588ffadccd485501d6dd7f2a613f20029ce6ae8c19e6cbc4b6817326710; retrieved 2026-09-16T02:23:14.104Z.