CEN11FA401 · Cirrus Design Corp SR22
Buds Aviation Cirrus Design Corp SR22 · Accident: loss of control in flight during takeoff
From Rickenbacker International Airport (LCK) to Caldwell, NJ
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN11FA401
- 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
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- 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
- N526PG
- Operator
- Buds Aviation
- Onboard fatalities
- Unknown
- Route
- From Rickenbacker International Airport (LCK), Columbus, OHTo Caldwell, NJ
- 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
- Takeoff
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After takeoff in instrument meteorological conditions, the airplane was cleared for a left turn. Shortly thereafter, the airplane entered a left climbing turn, and the pilot engaged the autopilot. The flight director subsequently commanded a right roll and a decrease in pitch attitude. (The GPS steering command was set to navigate to a waypoint, and the shortest way to get there was a turn to the right.) The airspeed decreased to 105 knots and the bank angle was over 45 degrees left-wing low, so the aural underspeed alert activated because of the risk of stall. The nose-up pitch attitude decreased through level flight and entered a nose-down attitude; the left bank angle continued to increase. The underspeed alert ceased when the airplane reached an airspeed of 141 knots; the airplane was at a maximum left bank angle of 72 degrees and a maximum nose-down attitude of 24 degrees. Recorded data showed the engine was producing power throughout the flight and the autopilot was operating normally. An examination of the engine and airplane revealed no evidence of mechanical malfunctions or failures that would have precluded normal operations. Given that the autopilot was set such that it would command a right turn when engaged, yet the pilot was instructed by the air traffic controller to turn left, it is likely that the pilot was overpowering the autopilot system to comply with the instructions. According to the airplane manufacturer, it would only take 17 pounds of force to override the autopilot in pitch and 3 to 5 pounds to override the roll. Further, given the instrument conditions that were present at the time, it is likely that the pilot experience spatial disorientation and did not recognize the effects of his inputs.
oxicological results indicated the pilot had taken a sedating medication at some point before the accident; however, the levels were such that a determination of the level of impairment was not possible.
Probable cause
The pilot's spatial disorientation during the takeoff into instrument meteorological conditions, which resulted in his failure to maintain control of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11FA401
- Event ID
- 20110619X03558
- Case number
- CEN11FA401
- 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. 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: 5147e5ebb4d01230be05fbf1aa2b4107433c881208bd175b887d43506d0b30ff; retrieved 2026-09-13T21:28:20.889Z.