FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA08FA026 · Cessna R182

7 Dec 2007 · Woodland, AL, United States

Executive Flight Center Cessna R182 · Accident: loss of control in flight

From Orlando Executive Airport (KORL) to Madison County Executive Airport-Tom Sharp Jr Field (KMDQ)

Report a problem

Event

NTSB case
MIA08FA026
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
2 · 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 R182

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
N2643C
Onboard fatalities
Unknown
Route
From Orlando Executive Airport (KORL), Orlando, FLTo Madison County Executive Airport-Tom Sharp Jr Field (KMDQ), Meridianville, AL
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
Unknown
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 in flight
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Flightcrew › Aircraft control, not maintained
  • Pilot in command › VFR flight into imc, inadvertent

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Without obtaining a formal weather briefing or filing a flight plan, the certified flight instructor (CFI) and student pilot departed on a long night cross country instructional flight back to their home airport following a business meeting that was attended by the student pilot. Reported and forecast marginal visual flight rules (MVFR) conditions, and areas of instrument meteorological conditions (IMC), prevailed along their intended route of flight. This information would have been given to the CFI and/or student pilot if they would have requested a formal preflight weather briefing.

Recorded radar data from the accident flight indicate that the airplane generally flew at an altitude that varied between 2,000 and 3,000 feet msl, which was consistent with an altitude that was intended to remain just below the reported scattered to broken layers of clouds along the route of flight. The flight path was along a nearly straight line to the destination airport. Due to radar coverage limitations, the radar data ended about 40 miles southeast of the accident site, when the airplane was flying about 2,200 feet msl, which was about 1,000 above the accident site elevation.

A witness who lived in the vicinity of the crash site stated he heard the airplane fly over his home, with the engine sounding as if was operating at high power, followed by an impact sound. Examination of the crash site revealed that the airplane collided with trees and terrain in a steep nose-down attitude, and at a high velocity. The engine and forward portion of the airplane were embedded about four feet into the ground.

Examination of the wreckage did not reveal any evidence of any preimpact mechanical malfunctions with the airframe, engine, or systems. Analysis of the wreckage and surrounding terrain revealed impact damage signatures consistent with a loss of aircraft control while under engine power. The direction of the impact was nearly opposite the intended route of flight. The flaps and landing gear were retracted, consistent with a cruise flight configuration. The accident site was located in remote, hilly terrain with very few lights. The accident occurred in dark night conditions, and in reduced visibility from a low cloud ceiling and possible localized fog. The airplane likely entered instrument meteorological conditions, or conditions in which a horizon was not visible, which led to a failure of the CFI and/or student pilot to maintain level flight. It is possible that the loss of control was precipitated by spatial disorientation; however, due to a lack of recorded radar data or flight recorder data at the time of the accident, the investigation could not determine whether the pilots became spatially disoriented. Additionally, the investigation could not determine who was manipulating the controls at the time of the loss of control; however, the CFI was the pilot-in-command of the airplane.

Review of the CFI and student pilot's chronological sleep patterns and duty day revealed that both pilots were susceptible to the effects of fatigue based on their sleep lengths during the 24 hours prior to the accident, and based on their time awake before the accident. Research has shown that human fatigue can degrade performance and judgment, and this likely impaired the performance and judgment of the CFI and student.

[ This report was modified on January 26, 2010 ]

Probable cause

The flight instructor’s failure to maintain control of the airplane while attempting to conduct visual flight in reduced visibility conditions at night. Factors contributing to the accident include the flight instructor’s inadequate preflight planning, and the impairment of both pilots due to fatigue.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA08FA026
Event ID
20071211X01926
Case number
MIA08FA026
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2007-12-08.
  • API snapshot SHA-256: f6ba2f456befa903da7a25d8912ca966fab7fcea9c456ece7eedd7ae0357a043; retrieved 2026-09-20T16:03:58.953Z.