CEN14CA381 · Cessna 150D
Indy Jet Center Cessna 150D · Accident: loss of control on ground during landing
From Indianapolis Regional Airport (MQJ) to Indianapolis Regional Airport (MQJ)
Event
- NTSB case
- CEN14CA381
- 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 150D
- 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
- N4545U
- Operator
- Indy Jet Center
- Onboard fatalities
- Unknown
- Route
- From Indianapolis Regional Airport (MQJ), Greenfield, INTo Indianapolis Regional Airport (MQJ), Greenfield, IN
- Aircraft age
- About 50 years (built 1964)
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot, who was on his second solo flight, reported that he maintained 68 mph and was on centerline of runway 25 with a slight left crosswind correction as he flared the airplane for landing. After touchdown, the airplane started drifting to the left. He reported that he attempted to correct the drift by applying rudder; however, he applied both the brakes and rudder causing the airplane to veer off the left side of the runway. The propeller impacted the ground, the nose gear collapsed, and the airplane nosed over, resulting in substantial damage to the firewall and fuselage. The student pilot reported that there was no malfunction or system failure of the airplane before the accident. The recorded wind at the airport was 170 degrees at 4 knots.
Probable cause
The student pilot failed to maintain directional control while landing with a crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA381
- Event ID
- 20140722X81231
- Case number
- CEN14CA381
- 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, 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: 64a8f95b2684282aed734d46541f57a3fe60c2447d2b2fdea66283e7634223fe; retrieved 2026-09-16T00:57:57.561Z.