WPR21LA082 · Cessna 560
Cessna 560 · Accident: medical event en route
From Portland Troutdale Airport (TTD) to Boise Air Terminal/Gowen Field (BOI)
Event
- NTSB case
- WPR21LA082
- 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
- 1 · 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
- Visual Meteorological Cond
Cessna 560
- Aircraft type
- Cessna 560
- 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
- N3RB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Portland Troutdale Airport (TTD), Troutdale, ORTo Boise Air Terminal/Gowen Field (BOI), Boise, ID
- Aircraft age
- About 32 years (built 1989)
- 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
- Medical event
- 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
- Not determined › Not determined
- Personnel issues › Physical
- 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
During the first 15 minutes of the flight, the pilot of the complex, high performance, jet airplane appeared to have difficulty maintaining the headings and altitudes assigned by air traffic controllers, and throughout the flight, responded intermittently to controller instructions. After reaching an altitude of 27,000 ft, the airplane began to deviate about 30° right of course while continuing to climb. The controller alerted the pilot, who did not respond, and the airplane continued to climb. Two minutes later, the airplane entered a tight, spiraling descent that lasted 8 minutes until the airplane impacted the ground at high speed in a right-wing-low attitude.
The airplane was highly fragmented on impact; however, examination did not reveal any evidence of structural failure, in-flight fire, a bird strike, or a cabin depressurization event, and both engines appeared to be producing power at impact.
Although the 72-year-old private pilot had extensive flight experience in multiple types of aircraft, including jets, he did not hold a type rating in the accident airplane, and the accident flight was likely the first time he had flown it solo. He had received training in the airplane about two months before the accident but was not issued a type rating and left before the training was complete. During the training, he struggled significantly in high workload environments and had difficulty operating the airplane’s avionics suite, which had recently been installed. He revealed to a fellow pilot that he preferred to “hand fly” the airplane rather than use the autopilot.
The airplane’s heading and flight path before the spiraling descent were consistent with the pilot not using the autopilot; however, review of the flight path during the spiraling descent indicated that the speed variations appeared to closely match the airplane’s open loop phugoid response as documented during manufacturer flight tests; therefore, it is likely that the pilot was not manipulating the controls during that time.
Review of the pilot’s medical history uncovered a number of conditions and medications that the pilot had not reported to the Federal Aviation Administration. The severity of injuries precluded obtaining any useful information regarding natural disease during autopsy, and no toxicology was performed. None of the pilot’s known medical conditions or medications would have directly caused incapacitation, but the pilot may have had undiagnosed disease or had some acute event that would have incapacitated him. His age, gender, high blood pressure, and hypertension placed him at risk for a heart attack or stroke. While the available evidence is consistent with a loss of airplane control following pilot incapacitation, the reason for his incapacitation could not be determined.
Probable cause
A loss of airplane control due to pilot incapacitation for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR21LA082
- Event ID
- 20210110102508
- Case number
- WPR21LA082
- 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, cause areas. 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: 4cafd7a6e4c7ef225c9ac907ba869ddf4ed377650c96a9d67d4e0a55ea21242d; retrieved 2026-09-15T07:24:22.453Z.