FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19FA240 · Beech F33 A

8 Aug 2019 · Hatboro, PA, United States

Beech F33 A · Accident: loss of control in flight en route

From Northeast Philadelphia Airport (PNE) to The Ohio State University Airport - Don Scott Field (OSU)

Report a problem

Event

NTSB case
ERA19FA240
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
3 · 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
Instrument Meteorological Cond

Beech F33 A

Aircraft type
Beechcraft 33
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
N4082S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Northeast Philadelphia Airport (PNE), Philadelphia, PATo The Ohio State University Airport - Don Scott Field (OSU), Columbus, OH
Aircraft age
About 44 years (built 1975)
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
En route · climb to cruise
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
Destroyed

Cause areas

  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The pilot departed just after sunrise on the instrument flight rules flight, which was the first takeoff of a multiday, cross-country trip. According to the National Transportation Safety Board performance study, which used automatic dependent surveillance-broadcast (ADS-B) data, and weather data, the airplane flew the runway heading after departure for about 1 minute and then likely entered the base of an overcast cloud layer, which extended from about 900 ft mean sea level (msl) to about 1,800 ft msl. After the airplane had been in the instrument meteorological conditions for about 20-30 seconds, the airplane banked right and deviated from the runway heading and then banked left, reaching its maximum recorded altitude of 1,186 ft msl. The airplane then began a steep descent at a rate of 2,000 ft/min while gaining airspeed. In the descent, the airplane banked right to about 30° right wing down before coming back to wings level just before the end of the data. The airplane’s final calculated airspeed was 180 kts and last recorded altitude was 586 ft msl, which was less than 1/4 mile from the accident site. A witness located near the accident site saw the airplane flying with the right wing low just before hearing an impact, and two witnesses described the engine as “loud.” The pilot's communication with air traffic control (ATC) was routine until the pilot communicated in error on the tower frequency while attempting to contact departure control, and he subsequently failed to check in with departure control as instructed. There was no distress call received from the pilot on either radio frequency. Postaccident examination of the airplane did not reveal any evidence of preimpact mechanical malfunctions that would have precluded normal operation. The wreckage debris path and propeller signatures, in addition to the witness statements, were consistent with the engine producing high power at the time of impact. The airplane's flight profile after it entered the clouds was consistent with the pilot experiencing spatial disorientation and subsequently losing airplane control. Several factors support this conclusion, which include the weather conditions likely restricting the pilot's visibility and the airplane’s abrupt roll and heading changes, which were followed by a steep accelerating vertical descent and a highly fragmented wreckage and debris path. A change from runway heading was not expected, as ATC had instructed the pilot to maintain runway heading, and the airplane had not reached the initial assigned altitude of 2,000 ft msl; thus, the abrupt changes in climb rate and roll/heading were contrary to ATC instructions. About the time of the roll and heading changes, it is also likely the pilot would have been distracted by his attempt to contact departure control on the correct frequency. It could not be determined why the pilot was unable to regain control after the airplane likely exited the cloud layer on the rapid descent; however, visibility along the route of flight was restricted by haze, mist, and likely sun glare, as the sun had just risen, and several witnesses described the light conditions as bright. It is likely that the autopilot was not engaged during the accident flight, given the flight instructor’s statement that the pilot usually did not engage the autopilot until cruise flight, coupled with the flight track data and the deviation in heading. In addition, review of the ADS-B data found that none of the likely preset roll, pitch, or airspeed limits of the airplane's flight envelope protection system were exceeded; thus, the protection system likely did not engage if it was turned on. Review of the pilot's medical records did not suggest a high risk for a sudden incapacitating event. While close family relations were unaware of any recent health problems, a fuel technician recalled that the pilot mentioned having chest pains the day before the accident, it is not clear if the pilot’s comment referred to heart pain or musculoskeletal chest pain. The autopsy of the pilot was limited by extensive injuries; thus, evidence of any acute processes or chronic conditions that would have placed the pilot at an increased risk of a sudden incapacitating event was unavailable, and the toxicology report did not find evidence of any impairing drugs. Given the available medical information, it could not be determined if the pilot had a medical condition that could have contributed to the cause of the accident.

Probable cause

The pilot's loss of airplane control due to spatial disorientation during the departure climb after entering instrument meteorological conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19FA240
Event ID
20190808X71425
Case number
ERA19FA240
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: investigation status, coordinates. 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: 5fd7f1e80ba565bbcdb25b600d1887f92288629f44dfaa5e507e19c6543eb796; retrieved 2026-09-15T07:03:13.019Z.