FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10CA283 · Cessna 182A

1 Jun 2010 · Franksville, WI, United States

Cessna 182A · Accident: flight instrument malfunction/failure during takeoff

From Cindy Guntly Memorial Airport (62C) to Cindy Guntly Memorial Airport (62C)

Report a problem

Event

NTSB case
CEN10CA283
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 182A

Aircraft type
Cessna 182
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
N4974D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cindy Guntly Memorial Airport (62C), Franksville, WITo Cindy Guntly Memorial Airport (62C), Franksville, WI
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
Takeoff
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
Flight instrument malfunction/failure
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 › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that the airspeed indicator was not displaying normal values as the airplane accelerated on the takeoff roll. After identifying the airspeed indicator anomaly, she continued the takeoff roll for an unspecified distance before ultimately deciding to abort the takeoff. The pilot noted that there was an accumulation of dew on the grass runway. During the rejected takeoff, the airplane overran the end of the runway and slid down an embankment before nosing-over in a ravine. Both wings were substantially damaged during the accident. A postaccident inspection revealed that the pilot had not removed the pitot-tube protective cover before departure.

Probable cause

The pilot’s inadequate preflight inspection and delay in aborting the takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10CA283
Event ID
20100601X20537
Case number
CEN10CA283
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2010-06-02.
  • API snapshot SHA-256: 46aa91f737dcb2beeba846fd8bc39296f07aa197152ec8185726be75a546da70; retrieved 2026-09-15T14:17:10.638Z.