The U.S. aircraft register, updated daily
Accidents · NTSB ERA24FA309 · Preliminary: the investigation is not finished

Cessna 208 accident near Youngstown, New York, July 20, 2024

On July 20, 2024 at about 3:40 pm local time, a 2002 Cessna 208, registered N1259K, was destroyed in an accident during enroute near Youngstown, New York. It was a skydiving flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
July 20, 2024 · about 3:40 pm local time
Place
Youngstown, New York · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 208 B, built 2002 · all 208s on the register
Registration
N1259K · registry record · serial 208B0974
Damage
Destroyed
Flight
Skydiving flight · general aviation rules (Part 91)

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

On July 20, 2024, about 1140 eastern daylight time, a Cessna 208B, N1259K, was destroyed when it was involved in an accident near Youngstown, New York. The commercial pilot was fatally injured. The airplane was operated by Skydive the Falls as a Title 14 Code of Federal Regulations Part 91 skydiving flight. The accident occurred on the second day of the Skydive the Falls Fest Boogie (Falls Fest) which the operator held annually at Windsor Airport (63NY), Youngstown, New York. The pilot had completed 5 uneventful flights on the morning of the accident. The accident occurred during the 6th flight after the parachutists had departed the airplane without incident. According to preliminary air traffic control (ATC) communications obtained from the Federal Aviation Administration (FAA), at 1135, the pilot reported to Buffalo Approach West Radar control that the flight was 2 minutes prior to the jump. At 1140, the controller attempted to terminate radar services with the airplane but received no response. At 1144, another company airplane, who was attempting to locate the accident airplane, noted smoke on the ground about 2 to 3 miles west of the jump zone. Review of preliminary ATC track data indicated that the airplane departed 63NY from runway 36, turned south and climbed to an altitude of 12,000 ft msl. The airplane subsequently made a jump pass from east to west over the airport. The track data ended near the west side of the airport, at 1139:20 at an altitude of 10,332 ft, an airspeed of 72 kts and a heading of 267º (see figure 1). Figure 1. Overhead flight track of accident airplane (N1259K). According to video imagery captured during the jump, after the skydivers departed the airplane, the airplane pitched over in a dive, and rolled right along its vertical axis before going out of view. A witness in the area observed the airplane descending rapidly “straight down,” towards the ground. Another witness observed the airplane with “one wing pointed towards the ground,” and “one wing pointed towards the sky;” the airplane impacted the ground, and debris was thrown up on to a roadway. Examination of the accident site and wreckage revealed that the airplane impacted a grassy slope adjacent to the Niagara Scenic Parkway in a left-wing, nose-low and near inverted attitude. A postimpact fire consumed most of the fuselage, the instrument panel, portions of the right wing and inboard section of the left flap. All primary and secondary flight control surfaces were identified except the inboard portion of the left flap. The outboard portion of the left flap exhibited thermal damage. Flight control cable continuity could not be established due to the condition of the wreckage. One loose cable was observed with signatures consistent with tensile overload. The elevator and elevator trim tab cables were attached to the bellcrank in the empennage. Both elevator trim tab actuators measured 2.4-inches, which corresponded to approximately 15°-17° tab up or full nose down travel. The left outboard elevator trim actuator screw assembly was bent upwards; the inboard actuator screw assembly was relatively straight. Both right elevator trim actuator screw assemblies were bent outboard; the outboard pushrod to the trim tab was fracture separated. The fuel system was mostly consumed by the postimpact fire. Both fuel caps were observed. The left cap was closed and secured to the left wing; the right cap was closed but loose from the wing. The turbine section fracture separated from the engine. Multiple blades were bent opposite the direction of rotation and several blades were flattened against the turbine shaft and exhibited smearing. The three propeller blades were separated from the hub, and the hub was not observed. One blade was located across the highway approximately 130 ft from the main wreckage. It was bent forward approximately 60° near the blade root and approximately 30° near the blade tip. The other two blades were located in the impact crater. One blade was bent forward at midspan with chordwise scratches on the blade back. The other blade was bent aft approximately 120° at the outer 1/3 of the blade with lengthwise scratches along the blade face. All three blades exhibited leading edge erosion. The pilot had been flying for the operator since April 2024. Her most recent FAA first-class medical certificate was issued on July 31, 2023. As of July 2024, she had accrued about 1,449 total hours of flight experience, about 102 of which were in the accident airplane make and model. According to FAA and airplane maintenance records, the airplane was manufactured in 2002. It had been modified via supplement type certificates (STCs) for parachute jump operations. The airplane's most recent 100-hour inspection was completed on March 24, 2024. At the time of the inspection, the airplane had accrued about 8,471 total hours of operation, and the engine had accrued about 1,050 hours since major overhaul. The wreckage was retained for further examination.

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. Unknown or undetermined during enroute defining event

The aircraft

  • Airframe total time: 8,471.3 hours
  • Last inspection: 100-hour inspection, March 22, 2024
  • Maximum gross weight: 8,750 lb
  • Seats: 12
  • Landing gear: fixed
  • Fire on the ground

The flight

  • Departed from: 63NY Youngstown NY at 3:20 pm
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 280° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 55°F (13°C)
  • Altimeter: 30.09 inHg
  • Observation at 10:53 am from KIAG, 10 miles away

Weather report (METAR): KIAG 201453Z 28006KT 10SM CLR 26/13 A3009 RMK AO2 SLP187 T02560128 58006

Injuries

FatalSeriousMinorNone
Flight crew1

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

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

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.