FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA508 · Cessna 170A

6 Aug 2009 · Aurora, IL, United States

Cessna 170A · Accident: loss of control on ground during landing

From Poplar Grove Airport (C77) to Aurora Municipal Airport (ARR)

Report a problem

Event

NTSB case
CEN09CA508
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 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
N9793A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Poplar Grove Airport (C77), Poplar Grove, ILTo Aurora Municipal Airport (ARR), Aurora, IL
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 · flare/touchdown
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot executed a normal traffic pattern for a "wheels landing" in the conventional landing gear airplane. After touchdown, the pilot applied a "little forward pressure to the yoke to keep the tail up..." The pilot reported the tail encountered a gust of wind from the left and he applied right rudder for correction. Subsequently, the airplane skidded off the left side of the runway and impacted a ditch. The right wing, right horizontal stabilizer, and fuselage sustained substantial damage. The pilot did not report any mechanical problems with the airplane.

Probable cause

The pilot's failure to maintain directional control during the landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA508
Event ID
20090810X24300
Case number
CEN09CA508
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: f0635734fa44d17b93132643e22fc8ae5b29ba71e8700db0d0a52065799d052f; retrieved 2026-09-15T12:46:31.896Z.