FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD99LA021 · Cessna 182E

25 Nov 1998 · Akron, OH, United States

Cessna 182E · Accident: forced landing during takeoff

From Akron Fulton International Airport (AKR) to Kent State University Airport (1G3)

Report a problem

Event

NTSB case
IAD99LA021
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 182E

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
N3396Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Akron Fulton International Airport (AKR), OHTo Kent State University Airport (1G3), Kent, OH
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 · rejected takeoff
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
Forced landing
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

  • Lubricating system, oil filler cap › Not secured
  • Pilot in command › Aircraft preflight, inadequate

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

NTSB narrative

After takeoff, about 300 feet above the ground, the airplane's windscreen was immediately covered with oil, restricting the pilot's forward visibility. The pilot aborted the take off and 'slipped the airplane back' onto the remaining 100 feet of the runway. He applied power to get over railway tracks at the end of the runway, the airplane went up an embankment, and slid to a stop on a grassy field. Examination of the wreckage revealed that the oil filler cap was tightly secured and the oil dip stick was still in position. The top cowling to the engine was removed, and no loose hoses were found. Utilizing the oil streaking left on the cowling and the windscreen, oil was traced from the windscreen, down to the top of the cowling, towards the access door for the oil filler, and then to the oil filler cap. The pilot was uncertain when he last added oil to the engine.

Probable cause

The pilot's inadequate preflight which resulted in a takeoff with the fuel cap unsecured.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD99LA021
Event ID
20001211X11445
Case number
IAD99LA021
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: 04fbff7ab53a7265b9f0b3d28fb97866486ef2a282797e5d27208882a509e383; retrieved 2026-09-21T20:38:50.198Z.