FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15FA009 · Raytheon Aircraft Company 58 UNDESIGNAT

12 Oct 2014 · Palos Hills, IL, United States

Raytheon Aircraft Company 58 UNDESIGNAT · Accident: loss of control in flight en route

From Chicago Midway International Airport (MDW) to Lawrence Municipal Airport (LWC)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN15FA009
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
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

Raytheon Aircraft Company 58 UNDESIGNAT

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
N31EW
Operator
Unknown
Onboard fatalities
Unknown
Route Possible conflict
From Chicago Midway International Airport (MDW), Chicago, ILTo Lawrence Municipal Airport (LWC), Lawrence, KS
Aircraft age
About 14 years (built 2000)
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The private pilot and two passengers departed in the multiengine airplane from a controlled airport under night, marginal visual flight rules conditions for a personal flight. Radar data showed the airplane climb to about 2,200 ft mean sea level (msl). At this altitude and when the airplane was about 3 nautical miles (nm) from the airport, it began a descending left turn, followed by a right turn, losing about 700 ft of altitude during this time. The airplane then began a climbing left turn. The left turn continued while its radius decreased until the end of the recorded data. During the final left turn, the airplane initially climbed about 400 ft, descended about 400 ft, and then climbed again about 1,300 ft before reaching its peak altitude of 2,800 ft msl. The final recorded radar point was 0.1 nm from the accident site, and the calculated descent rate between the final two radar points was more than 5,000 ft per minute. Postaccident examinations of the airframe, engines, and propellers, revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation. The airplane's avionics and instruments could not be functionally tested due to the extent of the impact damage.

The recorded weather conditions at the destination airport, located about 6 miles from the accident site, at the time of the accident included a broken ceiling at 1,000 ft above ground level (agl), an overcast ceiling at 1,700 ft agl, and visibility of 6 miles with mist. The radar data indicated that the airplane penetrated the cloud layers during the accident flight. The pilot held the appropriate certificates and ratings for operation of the multiengine airplane in instrument conditions, but no clearance had been issued for operation in instrument meteorological conditions. The weather and light conditions at the time of the accident were conducive to the development of spatial disorientation. Further, the flightpath, which was not consistent with the intended course; the airplane's repeated climbs and descents; and the loss of airplane control and high-speed impact were consistent with the known effects of spatial disorientation. Based on this evidence, it is likely that the pilot experienced spatial disorientation after the airplane entered the clouds at night, which led to his failure to maintain airplane control.

Probable cause

The pilot's loss of airplane control due to spatial disorientation while operating in night, instrument meteorological conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15FA009
Event ID
20141014X90107
Case number
CEN15FA009
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 2014-10-13.
  • API snapshot SHA-256: a01a4fda142450ee347d7d6ab38664488ce165be6d110d61d4e713a88f173651; retrieved 2026-09-14T17:27:28.655Z.