FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14LA451 · Cessna 177

23 Aug 2014 · Gordonville, TX, United States

Cessna 177 · Accident: loss of control on ground during landing

From Lakeview Airport (30F) to Cedar Mills Airport (3T0)

Report a problem

Event

NTSB case
CEN14LA451
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 177

Aircraft type
Cessna 177
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
N3202T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lakeview Airport (30F), Lake Dallas, TXTo Cedar Mills Airport (3T0), Gordonville, TX
Aircraft age
About 47 years (built 1967)
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

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

NTSB narrative

The pilot reported that he flew a visual approach with a left crosswind to a turf runway. As the airplane descended below a tree line, the wind decreased, and the airplane drifted left during the landing roll. The pilot applied right rudder, but the airplane did not respond. The airplane departed the left side of the runway and impacted multiple trees. Examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. After the accident, the pilot stated that he believed the passenger's foot might have blocked the rudder pedals. The accident is consistent with a loss of directional control during a crosswind landing.

Probable cause

A loss of directional control during a crosswind landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14LA451
Event ID
20140825X50740
Case number
CEN14LA451
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: 638dbe85dfdde4252ca3057ec0195ac95dc4f54d3bf1281f4f6a2dfe94dba580; retrieved 2026-09-16T01:40:49.928Z.