The U.S. aircraft register, updated daily
Accidents · NTSB WPR19FA230 · Final report

Cessna 560XL accident near Oroville, California, August 21, 2019

On August 21, 2019 at about 6:32 pm local time, a 2003 Cessna 560XL, registered N91GY, was destroyed in an accident during takeoff (rejected takeoff) near Oroville, California (Oroville Municipal airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 10 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to release the parking brake before attempting to initiate the takeoff, which produced an unexpected retarding force and airplane nose down pitching moment. Also causal was the flight crew’s delayed decision to abort the takeoff, which resulted in a runway excursion. Contributing to the accident was the lack of a NO TAKEOFF annunciation warning that the parking brake was engaged, and lack of a checklist item to ensure the parking brake was fully released immediately before takeoff.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 21, 2019 · about 6:32 pm local time
Place
Oroville, California · Oroville Municipal · map
Type
Accident
Injuries
No one was hurt; 10 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 560XL, built 2003 · all 560XLs on the register
Registration
N91GY · no longer on the register · serial 560-5314
Damage
Destroyed
Flight
Flight · charter and air-taxi rules (Part 135)

The NTSB's narrative final · quoted from the NTSB record

The crew was conducting an on-demand charter flight with eight passengers onboard. As the flight crew taxied the airplane to the departure runway, the copilot called air traffic control using his mobile phone to obtain the departure clearance and release. According to the pilot, while continuing to taxi, he stopped the airplane short of the runway where he performed a rudder bias check (the last item in the taxi checklist) and applied the parking brake without verbalizing the parking brake or rudder bias actions because the copilot was on the phone. After the pilot lined up on the runway and shortly before takeoff, the flight crew discussed and corrected a NO TAKEOFF annunciation for an unsafe trim setting. After the copilot confirmed takeoff power was set, he stated that the airplane was barely moving then said that something was not right, to which the pilot replied the airplane was rolling and to call the airspeeds. About 16 seconds later, the pilot indicated that the airplane was using more runway than he expected then made callouts for takeoff-decision speed and rotation speed. The pilot stated that he pulled the yoke back twice, but the airplane did not lift off. Shortly after, the pilot applied full thrust reversers and maximum braking, then the airplane exited the departure end of the runway, impacted a ditch, and came to rest 1,990 ft beyond the departure end of the runway. The airplane was destroyed by a postcrash fire, and the crew and passengers were not injured. Postaccident examination of the airplane and computed tomography scanning of the parking brake valve revealed it was in the ON position at the time of the accident. Calculations based on airplane performance data and airport surveillance video indicated that the accident airplane was able to accelerate to the speed required for the airplane to rotate and lift off as configured for a normal takeoff. However, the airplane’s performance was substantially degraded during the accident takeoff roll by an unexpected retarding force acting at the wheel/runway interface. Based on the parking brake valve examination and the performance of the airplane during the accident sequence, it is likely that the engaged parking brake produced the unexpected retarding force at the wheel/runway interface, and at a magnitude and direction that adversely affected the airplane’s acceleration and rotation capability during the attempted takeoff. Review of the airplane’s before takeoff and takeoff checklists revealed no explicit item that directed the flight crew to release or check the parking brake. The operator and manufacturer’s taxi checklists direct the flight crew to check brakes but do not specifically refer to the parking brake, and the operator’s flow diagram for that checklist did not point to the parking brake pull knob. Additionally, the position of the parking brake lever was not evaluated as part of the conditions that trigger a NO TAKEOFF annunciation. Review of the CE-560XL parking brake’s certification revealed that the parking brake was designed to prevent the airplane from rolling if one engine is at takeoff power and did not require a cockpit indication if the parking brake was not fully released. These conditions met the parking brake standard at the time of certification. However, the standard was updated in 2002 to require an annunciation if the parking brake was not fully released when takeoff power was applied, and the CE-560XL parking brake was not required to be updated to that standard. The manufacturer did not test the parking brake with both engines at takeoff power and was not required to as part of certification. The head of training where the pilot and copilot received their CE-560XL training stated that no airplane flight manual, checklist, or training curriculum provided a caution or warning that takeoff speeds may be achievable with full or partial pressure applied by the parking brake, and the pilot reported that he expected the airplane not to move with takeoff power applied. Available evidence, including continuous, heavy rubber deposits on the runway consistent with the main landing gear wheel spacing throughout the acceleration segment of the takeoff roll, indicates that it is likely that the pilot did not release the parking brake after setting it to perform the rudder bias check. Because the parking brake pull knob was located on the pilot’s left side and was obstructed from the copilot’s view, it is unlikely the copilot could have seen the pull knob before or during the takeoff. Although the crew was aware of the airplane’s slow acceleration, it was not clear at the time that it was related to an unexpected retarding force or the unsafe condition of the engaged parking brake. Had the parking brake lever position been incorporated into the conditions that trigger a NO TAKEOFF annunciation, as required for airplanes certificated after 2002, the pilot and copilot likely would have identified that the parking brake remained engaged and corrected the unsafe setting before attempting takeoff, just as they did for the unsafe trim setting. Despite the flight crew’s non-adherence to standard operating procedures, a checklist item that directed the pilot to fully release the parking brake before takeoff could have also served as an important redundancy to an annunciation, but none appears in the before takeoff checklist.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Runway excursion during takeoff (rejected takeoff) defining event

The NTSB's findings

  • Aircraft › Aircraft systems › Landing gear system › Brake › Incorrect use/operation
  • Personnel issues › Action/decision › Action › Delayed action › Flight crew
  • Aircraft › Aircraft systems › Landing gear system › Brake › Design
  • Personnel issues › Task performance › Use of equip/info › Use of equip/system › Flight crew
  • Aircraft › Aircraft systems › Indicating/recording systems › Central warning › Design
  • Organizational issues › Development › Design › Design of document/info › Manufacturer

Pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 6,482 hours in all; 192 in this make and model; 122 in the last 90 days; 41 in the last 30 days; 2,191 as pilot in command
  • Last flight review: May 10, 2019
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 4,748 hours in all; 858 in this make and model; 99 in the last 90 days; 27 in the last 30 days; 2,219 as pilot in command
  • Last flight review: August 7, 2019
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 9,876.6 hours
  • Last inspection: 100-hour inspection, April 12, 2019
  • Maximum gross weight: 20,200 lb
  • Seats: 10
  • Landing gear: retractable
  • Engine 1: Pratt & Whitney PW545A (turbofan); 0 hours total
  • Engine 2: Pratt & Whitney PW545A (turbofan); 0 hours total

The flight

  • Departed from: OVE Oroville CA at 6:32 pm
  • Destination: Portland OR
  • Flight plan: IFR
  • Runway 02, 6,020 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 82°F (28°C), dew point 57°F (14°C)
  • Altimeter: 29.94 inHg
  • Observation at 6:53 pm from KOVE

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers8

Documents from the investigation the NTSB's docket: the evidence folder behind the report

47 documents, released by the NTSB on March 7, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Group Chairman's Cockpit Voice Recorder Factual Report PDF, 32 pages View Download
2 Computed Tomography Specialist's Factual Report PDF, 25 pages View Download
3 Flight Data Recorder - Specialista��s Factual Report PDF, 10 pages View Download
4 Flight Data Recorder - Attachment 1 data file Download
5 Operations Group Factual Report PDF, 54 pages View Download
6 Ops Report Attachment 1 - PIC Written Statement PDF, 2 pages View Download
7 Ops Report Attachment 2 - PIC Interview Transcript - 1 PDF, 37 pages View Download
8 Ops Report Attachment 3 - PIC Interview Transcript - 2 PDF, 78 pages View Download
9 Ops Report Attachment 4 A�� SIC Interview Transcript #1 PDF, 41 pages View Download
10 Ops Report Attachment 5 - SIC Interview Transcript - 2 PDF, 40 pages View Download
11 Ops Report Attachment 6 - Flight Crewmember Activity Summary PDF, 3 pages View Download
12 Ops Report Attachment 7 A�� PIC Training Records PDF, 16 pages View Download
13 Ops Report Attachment 8 A�� SIC Training Records PDF, 29 pages View Download
14 Ops Report Attachment 9 - Takeoff and Landing Data Performance PDF, 2 pages View Download
15 Ops Report Attachment 10 - Dpj Provided Weight and Balance Information PDF, 8 pages View Download
16 Ops Report Attachment 11 A�� Investigation Weight and Balance Recreation PDF, 3 pages View Download
17 Ops Report Attachment 12 - Dpj Efb Program Application Excerpts PDF, 11 pages View Download
18 Ops Report Attachment 13 - Flight Crew Question and Answers on Efb Usage PDF, 2 pages View Download
19 Ops Report Attachment 14 - Dpj Background Information of Efb Usage PDF, 3 pages View Download
20 Ops Report Attachment 15 - CE-560XL Airplane Operating Manual Excerpts PDF, 12 pages View Download
21 Ops Report Attachment 16 - CE-560XL Airplane Flight Manual Excerpts PDF, 7 pages View Download
22 Ops Report Attachment 17 - Dpj CE-560XL SOP Excerpts PDF, 9 pages View Download
23 Ops Report Attachment 18 - CE-560XL Dpj Normal Checklist Procedures PDF, 2 pages View Download
24 Ops Report Attachment 19 - Dpj Fom Excerpts PDF, 28 pages View Download
25 Ops Report Attachment 20 - Dpj Review of Aviation Safety Action Program PDF, 1 page View Download
26 Ops Report Attachment 21 - Cae Head of Training Instructor Training Information PDF, 2 pages View Download
27 Ops Report Attachment 22 - Cae Engineering Simulator Performance Information PDF, 2 pages View Download
28 Systems Group Chairman's Factual Report PDF, 31 pages View Download
29 UAS Aerial Imagery-factual Report PDF, 11 pages View Download
30 UAS Aerial Imagery-attachment 1-ORTHOMOSAIC (Google Earth File Compressed) zip file Download
31 UAS Aerial Imagery-attachment 2-WRECKAGE GPS Item (Google Earth File) map file Download
32 UAS Aerial Imagery-attachment 3-VIDEO (Runway Flyover) video View Download
33 Aircraft Performance Study PDF, 166 pages View Download
34 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
35 NTSB Mfr - Passenger Statement Summaries PDF, 11 pages View Download
36 Security Camera Recordings Summary PDF, 3 pages View Download
37 Airport Security Camera Recording Courtesy of Table Mountain Aviation video View Download
38 Textron Response Letter - CVR Tones PDF, 1 page View Download
39 Statement of Party Representatives to NTSB Investigation - Textron PDF, 1 page View Download
40 Statement of Party Representatives to NTSB Investigation - Delta Private Jets PDF, 3 pages View Download
41 Photo Array PDF, 4 pages View Download
42 Flight Data Recorder Addendum - Specialist's Factual Report PDF, 1 page View Download
43 Flight Data Recorder Addendum - Attachment 1 data file Download
44 Flight Data Recorder Addendum - Attachment 2 data file Download
45 Flight Data Recorder Addendum - Attachment 3 data file Download
46 Flight Data Recorder Addendum - Attachment 4 data file Download
47 Textron Party Submission PDF, 5 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.