FTW00LA249 · Cessna 170A
Cessna 170A · Accident: loss of control on ground/water during landing
From F68 · Teague, TX to LXY
Event
- NTSB case
- FTW00LA249
- 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 170A
- Aircraft type
- Cessna 170
- 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
- N1447D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From F68 · Teague, TXTo LXY
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a short 15-minute flight, the student pilot encountered some light turbulence and windy flight conditions. While approaching mid-field at his destination, the 'windsock showed that the wind was blowing from the south.' He set up for a normal full flaps approach to Runway 18, and on final, the wind shifted to north-northeast. Upon touchdown, the airplane veered to the left. Control corrections were not effective, as the aircraft skidded off the runway to the left onto grass, and impacted a dirt mound at a 90-degree angle. The aircraft came to rest heading about 360 degrees. The main landing gears were sheared, the landing gear box was structurally damaged and the fuselage was buckled adjacent to the passenger side doorframe. The nearest full service weather reporting facility, located approximately 36 miles east of the accident site, reported wind from 090 at 13 knots, gusting to 19 knots.
Probable cause
The pilot's inadequate compensation for wind conditions. Factors were the gusty crosswind and the pilot's failure to perform a go-around upon encountering a windshift/crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA249
- Event ID
- 20001212X21970
- Case number
- FTW00LA249
- 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: 3d2b7e31e6d646bab291abffe8ee249b6a4f3429907f3ac7989ec1cf222849e4; retrieved 2026-09-22T12:28:57.440Z.