FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11FA074 · Beech A36

29 Nov 2010 · Theodore, AL, United States

Beech A36 · Accident: loss of control in flight while maneuvering

From St Elmo Airport (2R5) to St Elmo Airport (2R5)

Report a problem

Event

NTSB case
ERA11FA074
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
1 · 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
Instrument Meteorological Cond

Beech A36

Aircraft type
Beechcraft 36
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
N1860P
Operator
Michael S. Grantham · private individual
Onboard fatalities
Unknown
Route
From St Elmo Airport (2R5), St Elmo, ALTo St Elmo Airport (2R5), St Elmo, 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
Maneuvering
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 in flight
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 › Psychological

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

NTSB narrative

The pilot was conducting a night currency flight during marginal visual meteorological flight conditions. He did not file a flight plan or obtain a weather briefing prior to departure. About 4 minutes after departing, the pilot contacted air traffic control and stated the weather was worse than he anticipated. He requested an instrument clearance and approach back to his departure airport. The airplane was radar identified, the pilot was instructed to climb to 2,000 feet and then proceed direct to an intermediate fix. The pilot acknowledged the clearance and there was no further communication between him and the controller. A review of radar data revealed the airplane was first observed at 700 feet mean sea level, in a climbing right turn. It continued to climb while turning to the left and right, to 1,100 feet. The airplane was last observed by radar at 700 feet in a descending right turn.

A witness stated he observed the airplane flying below a cloud layer estimated between 500 to 1,000 feet agl, with the strobe lights on. He described the area as very dark with no ambient light. Another witness stated he observed the airplane in straight and level flight, flying in and out of the clouds.

The pilot's last recorded night flight was 14 months prior to the accident, and no flights had been conducted in the accident airplane. The pilot obtained an instrument rating 2 months before the accident and he had flown 4.5 hours of actual instrument flight time; of which, 1 hour was in another model airplane. The pilot had logged 15 minutes of instrument flight time in the accident airplane.

At the time of the accident, the moon's phase was "waxing crescent" with 18 percent of the disk illuminated. If neither horizon nor surface references exist, the attitude of an airplane must be determined by artificial means from the flight instruments. However, during periods of low visibility, the supporting senses sometimes conflict with what is seen, and when this happens, a pilot is particularly vulnerable to spatial disorientation. Federal Aviation Administration guidance indicates that spatial disorientation can occur when there is no natural horizon or surface reference, such as a night flight in sparsely populated areas similar to that of the accident area and conditions. Based on the wreckage and the visual reference conditions present at the time of the accident it is likely that the pilot experienced spatial disorientation.

Examination of the airframe, flight controls, engine assembly and accessories revealed no pre-impact mechanical anomalies.

Probable cause

The pilot's failure to maintain aircraft control while maneuvering at night in deteriorating weather conditions due to spatial disorientation. Contributing to the accident was the pilot's failure to obtain a weather briefing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11FA074
Event ID
20101130X83110
Case number
ERA11FA074
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-11-30.
  • API snapshot SHA-256: 6ebf4c8eba04abd5e9068990c2d32f897312d3d3a1933521bf84b0dc35d43565; retrieved 2026-09-13T21:09:57.471Z.