FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC08MA090 · Raytheon Aircraft Company C90A

1 Feb 2008 · Mount Airy, NC, United States

Blue Sky Airways Raytheon Aircraft Company C90A · Accident: aerodynamic stall/spin on approach

From Polk County Airport- Cornelius Moore Field (4A4) to Mount Airy Surry County Airport (MWK)

Report a problem

Event

NTSB case
NYC08MA090
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
6 · 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 C90A

Aircraft type
Beechcraft 90
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
N57WR
Onboard fatalities
Unknown
Route
From Polk County Airport- Cornelius Moore Field (4A4), Cedartown, GATo Mount Airy Surry County Airport (MWK), Mount Airy, NC
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 missed 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
Aerodynamic stall/spin
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 › Task performance

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

NTSB narrative

While flying a nonprecision approach, the pilot deliberately descended below the minimum descent altitude (MDA) and attempted to execute a circle to land below the published circling minimums instead of executing the published missed approach procedure. During the circle to land, visual contact with the airport environment was lost and engine power was never increased after the airplane had leveled off. The airplane decelerated and entered an aerodynamic stall, followed by an uncontrolled descent which continued until ground impact. Weather at the time consisted of rain, with ceilings ranging from 300 to 600 feet, and visibility remaining relatively constant at 2.5 miles in fog. Review of the cockpit voice recorder (CVR) audio revealed that the pilot had displayed some non professional behavior prior to initiating the approach. Also contained on the CVR were comments by the pilot indicating he planned to descend below the MDA prior to acquiring the airport visually, and would have to execute a circling approach. Moments after stating a circling approach would be needed, the pilot received a sink rate aural warning from the enhanced ground proximity warning system (EGPWS). After several seconds, a series of stall warnings was recorded prior to the airplane impacting terrain. EGPWS data revealed, the airplane had decelerated approximately 75 knots in the last 20 seconds of the flight. Examination of the wreckage did not reveal any preimpact failures or malfunctions with the airplane or any of its systems. Toxicology testing detected sertraline in the pilot’s kidney and liver. Sertraline is a prescription antidepressant medication used for anxiety, obsessive-compulsive disorder, panic disorder, posttraumatic stress disorder, and social phobia. The pilot’s personal medical records indicated that he had been treated previously with two other antidepressant medications for “anxiety and depression” and a history of “impatience” and “compulsiveness.” The records also documented a diagnosis of diabetes without any indication of medications for the condition, and further noted three episodes of kidney stones, most recently experiencing “severe and profound discomfort” from a kidney stone while flying in 2005. None of these conditions or medications had been noted by the pilot on prior applications for an airman medical certificate. It is not clear whether any of the pilot’s medical conditions could account for his behavior or may have contributed to the accident.

Probable cause

The pilot's failure to maintain control of the airplane in instrument meteorological conditions. Contributing to the accident were the pilot's improper decision to descend below the minimum descent altitude, and failure to follow the published missed approach procedure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC08MA090
Event ID
20080211X00169
Case number
NYC08MA090
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: 235ca81b85819fdf5cf19e7576d903838c98f04f2f43ab019876614548bdf205; retrieved 2026-09-13T18:55:24.766Z.