MIA08MA051 · Cessna 525
Cessna 525 · Accident: loss of control in flight en route
From Augusta State Airport (AUG) to Lincoln Airport (LNK)
Event
- NTSB case
- MIA08MA051
- 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
- 2 · 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
Cessna 525
- Aircraft type
- Cessna 525
- 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
- N102PT
- Operator
- Jeanette A. Symons · private individual
- Onboard fatalities
- Unknown
- Route
- From Augusta State Airport (AUG), West Gardiner, METo Lincoln Airport (LNK), Lincoln, NE
- 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
- 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 › Action/decision
- 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
The instrument-rated private pilot departed on an instrument flight rules (IFR) cross-country flight plan in near-zero visibility with mist, light freezing rain, and moderate mixed and clear icing. After departure, and as the airplane entered a climbing right turn to a track of about 260 degrees, the pilot reported to air traffic control that she was at 1,000 feet, climbing to 10,000 feet. The flight remained on a track of about 260 degrees and continued to accelerate and climb for 38 seconds. The pilot then declared an emergency, stating that she had an attitude indicator failure. At that moment, radar data depicted the airplane at 3,500 feet and 267 knots. Thirteen seconds later, the pilot radioed she wasn't sure which way she was turning. The transmission ended abruptly. Radar data indicated that at the time the transmission ended the airplane was in a steep, rapidly descending left turn. The fragmented airplane wreckage, due to impact and subsequent explosive forces, was located in a wooded area about 6 miles south-southwest of the departure airport. Examination of the accident site revealed a near vertical high-speed impact consistent with an in-flight loss of control. The on-site examination of the airframe remnants did not show evidence of preimpact malfunction. Examination of recovered engine remnants revealed evidence that both engines were producing power at the time of impact and no preimpact malfunctions with the engines were noted.
The failure, single or dual, of the attitude indicator is listed as an abnormal event in the manufacturer's Pilot's Abbreviated Emergency/Abnormal Procedures. The airplane was equipped with three different sources of attitude information: one incorporated in the primary flight display unit on the pilot's side, another single instrument on the copilot's side, and the standby attitude indicator. In the event of a dual failure, on both the pilot and copilot sides, aircraft control could be maintained by referencing to the standby attitude indicator, which is in plain view of the pilot. The indicators are powered by separate sources and, during the course of the investigation, no evidence was identified that indicated any systems, including those needed to maintain aircraft control, failed.
The pilot called for a weather briefing while en route to the airport 30 minutes prior to departure and acknowledged the deteriorating weather during the briefing. Additionally, the pilot was eager to depart, as indicated by comments that she made before her departure that she was glad to be leaving and that she had to go. Witnesses indicated that as she was departing the airport she failed to activate taxi and runway lights, taxied on grass areas off taxiways, and announced incorrect taxi instructions and runways. Additionally, no Federal Aviation Administration authorization for the pilot to operate an aircraft between 29,000 feet and 41,000 feet could be found; the IFR flight plan was filed with an en route altitude of 38,000 feet.
The fact that the airplane was operating at night in instrument meteorological conditions and the departure was an accelerating climbing turn, along with the pilot's demonstrated complacency, created an environment conducive to spatial disorientation. Given the altitude and speed of the airplane, the pilot would have only had seconds to identify, overcome, and respond to the effects of spatial disorientation.
Probable cause
The pilot's spatial disorientation and subsequent failure to maintain airplane control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA08MA051
- Event ID
- 20080211X00172
- Case number
- MIA08MA051
- 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: cd8899927c2b2302cd37a24656689ac097b5a78b9fd396d5085f4f6f97bcd9ce; retrieved 2026-09-13T18:55:40.556Z.