DFW06CA004 · Cessna 172
Cessna 172 · Accident: loss of control on ground/water during landing
From David Wayne Hooks Memorial Airport (DWH) to David Wayne Hooks Memorial Airport (DWH)
Event
- NTSB case
- DFW06CA004
- 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 172
- 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
- N94JA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From David Wayne Hooks Memorial Airport (DWH), Houston, TXTo David Wayne Hooks Memorial Airport (DWH), Houston, 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
- 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 › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 13-hour student pilot lost directional control of the airplane during his initial solo flight while on his third touch-and-go landing on Runway 17R. The student pilot reported that right after touchdown, the airplane exited the left side of the runway, passed through a grass median, crossed parallel taxiway "foxtrot" and impacted a taxiway sign, coming to rest in the inverted position. In a telephone conversation with the NTSB investigator in charge (IIC) the student pilot added that the airplane "abnormally veered to the left" after touching down. The student pilot further stated that he retracted the flaps and added power for the go-around after the airplane started to veer left. He did not recall if he had applied brakes during the landing roll. Runway 17R is 7,008-feet long and 100-feet wide. The winds at the time of the accidents were from 050 degrees at 7 knots. Multiple attempts to obtain a completed Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) from the pilot were unsuccessful.
Probable cause
The pilot's failure to maintain directional control while landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW06CA004
- Event ID
- 20051130X01910
- Case number
- DFW06CA004
- 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, 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: 0786222e4d91615fbadeec68484b38e0894abaa34da0768c84a620c4d2356e37; retrieved 2026-09-22T05:18:11.488Z.