FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11FA107 · Beech 58P

5 Jan 2011 · Birmingham, AL, United States

Beech 58P · Accident: loss of control in flight on approach

From Morristown Municipal Airport (MMU) to Shelby County Airport (EET)

Report a problem

Event

NTSB case
ERA11FA107
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 58P

Aircraft type
Beechcraft 58
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
N48TS
Operator
William E Scott · private individual
Onboard fatalities
Unknown
Route
From Morristown Municipal Airport (MMU), Morristown, NJTo Shelby County Airport (EET), Alabaster, 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
Approach · IFR final approach
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 › Psychological

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

NTSB narrative

During the approximately 5 hour and 25 minute night instrument cross-country flight in a multi-engine airplane, the pilot elected not to stop at his planned fuel stop. Upon reaching the destination airport, the weather conditions included an overcast ceiling at 300 feet and 2 miles visibility in drizzle, which were worse than the forecast conditions of overcast ceiling at 1,000 feet and 6 miles visibility. The pilot diverted to his planned alternate airport and attempted an instrument landing system approach. Given the lack of a fuel stop, the pilot may have felt personal pressure to land the airplane as soon as possible. The airplane initially intercepted the localizer for the approach, but did not intercept the glideslope. The airplane then proceeded left of course, above the glideslope, followed by a continued left deviation and descent below the glideslope. The tower controller asked the pilot if he was still on the localizer course and the pilot replied that he was not. The tower controller then provided heading and altitude instructions in an attempt to guide the pilot onto a missed approach. The pilot acknowledged the heading instruction, but failed to turn to the assigned heading or climb to the assigned altitude. The airplane subsequently impacted a residential area about 1/2 mile from the runway.

The pilot's logbook was not recovered and a determination of his flight experience in actual instrument conditions could not be made. According to a flight instructor, the pilot had owned the accident airplane for about 6 months and had 80 to 90 hours in the make and model. The pilot completed an instrument proficiency check with the instructor about 1 month prior to the accident. The instruction included many instrument approaches and missed approach procedures. Additionally, the flight instructor concentrated on attitude flying, which was not the pilot's strongest skill.

Examination of the wreckage did not reveal any preimpact mechanical malfunctions. 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; when this happens, a pilot is particularly vulnerable to disorientation. Postmortem toxicology testing noted findings consistent with marijuana use; however, no blood was available for toxicological testing and it was not possible to reliably estimate when the marijuana may have most recently been used or whether the pilot may have been impaired by such use.

Probable cause

The pilot's failure to maintain control of the airplane during an instrument approach due to spatial disorientation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11FA107
Event ID
20110105X11652
Case number
ERA11FA107
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2011-01-06.
  • API snapshot SHA-256: 551deb8ed0fe31e52e7510e8b1a32484f5691e41cb4d194e021eb6d8f840b4c2; retrieved 2026-09-13T21:12:16.095Z.