Thursday, August 22, 2019

Cessna 560XL Citation Excel, N91GY: Accident occurred August 21, 2019 at Oroville Municipal Airport (KOVE), Butte County, California

The National Transportation Safety Board traveled to the scene of this accident.

Additional Participating Entity:
Federal Aviation Administration / Flight Standards District Office; Sacramento, California
Textron Aviation Inc; Wichita, Kansas

Aviation Accident Preliminary Report - National Transportation Safety Board:

Location: Oroville, CA
Accident Number: WPR19FA230
Date & Time: 08/21/2019, 1132 PDT
Registration: N91GY
Aircraft: Cessna 560XL
Injuries: 10 None
Flight Conducted Under: Part 135: Air Taxi & Commuter - Non-scheduled

On August 21, 2019, about 1132 Pacific daylight time, a Cessna 560XL airplane, N91GY, overran the departure end of runway 2 following a rejected takeoff from Oroville Municipal Airport (OVE), Oroville, California. The two airline-transport pilots and 8 passengers were not injured. The airplane was destroyed by a post-crash fire that consumed a majority of the airplane. The airplane was registered to Jotts LLC, and was operated by Delta Private Jets, as a Title 14 Code of Federal Regulations Part 135 on-demand charter flight. Visual meteorological conditions prevailed, and an instrument flight rules flight plan was filed. The flight was originating at the time of the accident and was destined for Portland International Airport (PDX), Portland, Oregon.

The pilot flying reported that prior to takeoff, they had a waypoint fix and departure change, which he updated within the flight management system. As they taxied onto runway 2, he called for the before takeoff checklist. Following completion of the checklist, they initiated takeoff, and the non-flying pilot called "airspeed alive," V1, and Vr. The pilot flying stated that "it was just a weird sensation" as he pulled the yoke back and the airplane didn't lift off. The pilot flying further stated that he pulled the yoke back a second time and noticed no movement of the nose. Shortly after, the non-flying pilot called for an abort, and the pilot flying applied full thrust reversers and maximum braking. Subsequently, the airplane exited the departure end of the runway, impacted a ditch, and skidded across a grass covered area, where a post impact fire ensued.

Review of surveillance video from a fixed-based operator (FBO) located at OVE showed the airplane holding short of runway 2 for about 3 minutes, 44 seconds. The airplane then taxied forward toward runway 2, stopped, and remained stationary for about 18 seconds, until it began to taxi again onto the runway. After lining up on the runway, the airplane remained stationary for about 16 seconds. Once the takeoff roll was initiated, the airplane traveled out of the camera frame 48 seconds later. The position where the airplane moves out of the camera frame was about 730 ft beyond the departure end of runway 2.

Examination of the accident site revealed that the airplane came to rest about 1,990 ft beyond the departure end of runway 2, on a heading of about 060° magnetic. See Figure 1. Review of a photo taken by a witness prior to the airplane being consumed by the fire, revealed that the airplane was mostly intact and resting on the underside of the fuselage and wings. Examination of the runway revealed tire transfer marks which originated from the runway 2 hold short line and progressed onto the runway, and continued throughout the entire length of the runway, overrun, adjacent runway, grassy area, taxiway, and grassy area near the main wreckage. The wreckage was recovered to a secure location for further examination.

Figure 1: View of the accident site and runway environment.

Aircraft and Owner/Operator Information

Aircraft Make: Cessna
Registration: N91GY
Model/Series: 560XL
Aircraft Category: Airplane
Amateur Built: No
Operator: Delta Private Jets
Operating Certificate(s) Held: On-demand Air Taxi (135) 

Meteorological Information and Flight Plan

Conditions at Accident Site: Visual Conditions
Condition of Light: Day
Observation Facility, Elevation: KOVE, 190 ft msl
Observation Time: 1853 UTC
Distance from Accident Site: 0 Nautical Miles
Temperature/Dew Point: 28°C / 14°C
Lowest Cloud Condition: Clear
Wind Speed/Gusts, Direction: Light and Variable / , Variable
Lowest Ceiling: None
Visibility:  10 Miles
Altimeter Setting: 29.94 inches Hg
Type of Flight Plan Filed: IFR
Departure Point: Oroville, CA (OVE)
Destination: Portland, OR

Wreckage and Impact Information

Crew Injuries: 2 None
Aircraft Damage: Destroyed
Passenger Injuries: 8 None
Aircraft Fire: None
Ground Injuries: N/A
Aircraft Explosion: None
Total Injuries: 10 None
Latitude, Longitude: 39.497222, -121.616667 (est)

OROVILLE — A plane crash at the Oroville Airport ignited a wildfire near the runways.

The crash, reported around 11:30 a.m. today caused a fire which the Oroville Fire Department and Cal Fire-Butte County are fighting.

By the time Oroville firefighters got to the crash at the north end of the runway, the plane was completely engulfed in flames, said Oroville Public Safety Director Joe Deal.

The 10 people inside — eight passengers and two pilots — all made it out of the downed plane without any injuries, Deal said.

Once firefighters accounted for everyone who had been in the plane, they turned their attention to fighting the wildfire.

Cal Fire-Butte County Public Information Officer Rick Carhart said the grass fire was quickly put out and the plane itself was doused with water.

The jet plane had just been refueled with 480 pounds of fuel, Deal said.

The CHP closed a portion of Highway 162 near the airport because there was a fear that spilled fuel could ignite.

Willows resident John Cecil took photos and videos of the plane on fire and said he heard what sounded like explosions.

Deal was proud of the emergency teams for getting the word out quickly and keeping people in the area informed of what was going.

The Federal Aviation Administration will be looking further into the crash, Deal said.

A crew from the Chico Fire Department also helped by spraying the burned wreckage with fire-suppressing foam shortly after 1 p.m.

Story and video ➤


  1. You think they should have shut the engines down before evacuation of the aircraft.

  2. What information do you have that says they did not shut engines down upon evacuation? Further, maybe they could not shut engines down, that has happened before where controls or signals are lost so pilots cannot shut engines down.

  3. I thought the same thing based on the noise in the video ... Sounded like they were running.

    Engine shutdown is on every evac checklist I have ever seen.

    Agree there could have been a mechanical issue that prevented the shutdown.

    Glad everybody got out okay.

  4. Darren - Look at the smoke from the grass fire directly aft of the aircraft vs smoke from the area of the right wing root. The smoke aft of the aircraft is being blown rearward. At least one engine is running. That might be part of why they went off.

  5. Thanks for that is a good catch/eye on your part. I had not heard any of the audio yet, bet will check it out. The NTSB has issued their preliminary brief on this crash. Not too much which is significant except the fact after two (2) bounces, they touched down with only 1,000 feet RW remaining. Here is the preliminary:

  6. Wrong accident Darren. You are talking about Earnhardt’s.. This is not that one. This one was on takeoff.

  7. Correct, sorry, I was doing 15 other things when I posted this and meant to say that the NTSB had issued a preliminary brief of the Earnhardt Citation Latitude crash. Completely different crashes though similar in both were overruns (Earnhardt's Latitude was a landing crash, the Excel for this subject material crash was a takeoff with RTO. Sorry if I added to any confusion. Amazing to me the pilots + pax got out on both the crashes in Citations, truly amazing.

  8. No need to apologize. We are all human. Yes it it amazing no serious injuries.

  9. The noise from the video could be coming from an APU running behind the camera on the ramp. Or, it could be from the APU on the plane itself. I doubt they failed to shut the engines down, but they possibly could have forgotten the APU (a mistake that is easily understandable given the situation. However, the way the pilots were moving about around the airplane, If that was their APU running, one of them would have jumped back in there and hit the switch (would have taken about 5")

  10. The new photo posted at the top of the article shows the right TR deployed, and the left TR stowed. Might be a sign of a contributing issue?