FTW96LA182 · Cessna 172N
Mile High Aviation SVC Cessna 172N · Accident: loss of control on ground/water during landing
From Rocky Mountain Metropolitan Airport (BJC) to Rocky Mountain Metropolitan Airport (BJC)
Event
- NTSB case
- FTW96LA182
- 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 172N
- Aircraft type
- Cessna 172
- 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
- N75839
- Operator
- Mile High Aviation SVC
- Onboard fatalities
- Unknown
- Route
- From Rocky Mountain Metropolitan Airport (BJC), COTo Rocky Mountain Metropolitan Airport (BJC)
- 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
- Landing · landing roll
- 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 on ground/water
- 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 › Compensation for wind conditions, inadequate
- Pilot in command › Directional control, not obtained/maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was on downwind leg to runway 11L when the control tower operator advised the pilot that wind velocity had increased to 15 knots. On final approach, the pilot was advised the wind velocity had dropped to 5 knots. The pilot said the airplane was then to the left of the runway centerline, and he maneuvered to correct the alignment. The airplane touched down with a side load because the nose was not pointed down the runway. The airplane departed the left side of the runway onto a high speed turnoff, crossed a parallel taxiway and struck the taxiway sign. The nose landing gear collapsed and the airplane came to a halt on the parking ramp. The wind was reported to be from 070 degrees at 10 knots, with gusts to 16 knots.
Probable cause
the student pilot's inadequate compensation for wind conditions, and his failure to obtain/maintain directional control. A factor was the cross wind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA182
- Event ID
- 20001208X05569
- Case number
- FTW96LA182
- 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: abe25bbeca444a5b48afdc891b148c3e781063d070c29439912653b82cd602f2; retrieved 2026-09-22T22:35:13.602Z.