2025 North Carolina Cessna Citation II crash
GB Aviation Leasing Cessna 550 · Crashed during failed emergency landing attempt, under investigation
From Statesville Regional Airport (SVH) to Sarasota Bradenton International Airport (SRQ)
Event
- NTSB case
- WPR26MA063
- 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
- Ongoing
- Event fatalities
- 7 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 7
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- 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
Cessna 550
- Aircraft type
- Cessna 550
- 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
- N257BW
- Operator
- GB Aviation Leasing
- Onboard fatalities
- Unknown
- Route
- From Statesville Regional Airport (SVH)To Sarasota Bradenton International Airport (SRQ), Sarasota, FL
- Aircraft age
- About 44 years (built 1981)
- 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
- Landing
- 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
- Landing area undershoot
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
From the Wikipedia article
On December 18, 2025, a Cessna 550 Citation II business jet crashed in Statesville, North Carolina. The crash occurred between 10:15 and 10:20 a.m. local time. Seven people were killed in the crash, including former NASCAR driver Greg Biffle, his wife and his two children.
Background
Statesville is about 45 mi north of Charlotte. Statesville Airport is a small regional airport without a control tower.
Shortly after the crash, low clouds and light rain were reported in the area. The area had a visibility of less than three miles.
The plane, a Cessna C550 business jet, was owned by GB Aviation Leasing LLC, which was owned by retired NASCAR driver Greg Biffle. The plane had the tail number N257BW and was manufactured in 1981. Flight records show that the plane was scheduled to fly to Florida and spend most of the rest of the day there. The plane had seven occupants.
Crash
The plane departed from Statesville Airport from runway 10 at 10:06 a.m. and traveled around 11 mile before turning sharply to the left back towards the airport. The plane reached a maximum altitude of 4300 ft. Upon returning to the airport, the plane crashed at the east side of the runway while attempting to land.
Investigation and cause
Investigation
The cockpit voice recorder (CVR), ground proximity warning system, a Garmin GTN 750 display and various cockpit instruments were recovered by an NTSB team. The NTSB began an investigation into the incident. Two briefings were held by the NTSB. A preliminary report has been released, but the final report will be expected to take 12 to 24 months.
The preliminary report was released on January 30, 2026. Cockpit voice recordings and ground witnesses revealed that the left engine did not start on the first attempt, and the captain and right-seat pilot-passenger discussed a malfunctioning thrust reverser indicator, but the reversers themselves appeared functional. The captain acted as pilot flying while the pilot-passenger acted as pilot monitoring, handling radio calls and checklists.
As the aircraft was not equipped with a flight data recorder (FDR), the preliminary report analyzes the accident sequence using data recorded by the Garmin GTN 750 and conversations recorded on the CVR. After the plane began to descend, a pilot-passenger said that there were temperature reading discrepancies between the engines, but the issue was not discussed further. The captain reported problems with the Garmin's altimeter, which then stopped recording altitude data, and stopped recording heading data a short time later. The right-seat pilot-passenger took the controls momentarily before the captain resumed control, turned back towards the airport, and called for flap and landing gear extension, but the flap and landing gear lights were not illuminated. A passenger asked if the alternator (which generates electrical power) was functioning properly, and although the Cessna 550 is not equipped with an alternator (it has a generator), the captain responded that it was the "problem" and the Garmin resumed functioning immediately afterwards. The plane continued to descend and lose airspeed as it turned to runway heading, and then struck a 29 ft approach light structure about 1,380 ft from the runway. The plane struck additional light structures and trees before coming to rest 400 ft from the end of the runway in the runway overrun area. The fuselage was largely consumed by fire. The NTSB said there was no evidence of structural failure, fan blade damage to the engines was consistent with rotation on impact, and the engines remained attached to the airframe.
Text from the Wikipedia article “2025 North Carolina Cessna Citation II crash” (revision 1372037990, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
On December 18, 2025, at 1015 eastern standard time, a Cessna Citation 550, N257BW, was destroyed when it was involved in an accident near Statesville, North Carolina. The pilot and 6 passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. The airplane was positioned on the south parking ramp at Statesville Regional Airport (SVH), Statesville, North Carolina, for passenger loading and preflight. Ground personnel reported the airplane was fully fueled prior to the flight. Cockpit Voice Recorder (CVR) audio began recording the accident flight at 0944:21. The CVR recording confirmed the airline transport rated pilot was seated in the left seat, the pilot’s adult son, who held a private pilot certificate with a single engine land and an instrument rating, was a passenger in the right seat. A rear seat passenger with a private pilot certificate and ratings for multi-engine land, instrument airplane, and rotorcraft-helicopter was positioned near the cockpit in the cabin area. Engine start was initiated using onboard battery power and, following an initial unsuccessful start of the left (no. 1) engine, both engines were started about 0953. The airplane taxied from the south parking area at 0959, crossed runway 10/28 at midfield, and taxied to the approach end of runway 10. During taxi, the pilot and the two pilot-rated passengers discussed that a thrust reverser indicator light(s) for an unspecified engine was inoperative, but that the thrust reverser for the affected engine was working properly. The airplane departed from runway 10 at SVH, under visual flight rules (VFR) about 1006. The pilot intended to activate an instrument flight rules (IFR) flight plan, with a planned destination of Sarasota/Bradenton International Airport (SRQ), Sarasota, Florida, once airborne. The pilot performed the takeoff and departure while the right seat passenger performed various checklists and communicated on the radio. During takeoff roll, the rear passenger commented that the left engine was producing more power than the right and indicated there may have been a faulty gauge. The pilot continued the takeoff. Preliminary GPS data showed the airplane made a climbing left turn following takeoff. At 1007:19 the pilot commented that he would remain VFR until they received their IFR clearance. At 1008, the airplane had turned about 180° and attained an altitude of about 2,200 ft mean sea level (msl). The airplane continued to turn left and began to descend. The right-seat passenger attempted to contact ZTL ATC and activate the flight’s IFR flight plan three times between 1008 and 1010 but was unsuccessful due to the controller’s workload and associated radio communications. About 1009 there was discussion between the pilot and rear passenger about climbing to a higher altitude, even though they were technically required to remain VFR. The airplane had descended to about 1,580 ft msl and was established on a heading of about 250° and 164 knots (kts) indicated airspeed (IAS) at that time. The pilot initiated a climb, and shortly after, the rear passenger noted a difference between the left and right engine interstage turbine temperature (ITT) indications. There were no further discussions regarding the engine instruments throughout the remainder of the CVR recording. The autopilot was either disengaged intentionally, or it disengaged independently at 1010:02. Beginning at 1010:14 no intelligible CVR audio was captured from the left seat hot microphone and audio panel for the next 3 minutes and 55 seconds. Starting at 1010:18, the cockpit area microphone captured the pilot making remarks indicating his altitude indicator was not working properly and that additional left side flight instruments may not have been working properly. The Garmin GTN-750 stopped recording airspeed data at 1009:37 and heading data at 1010:58. About 1011, airplane control was transferred to the right seat passenger, at an altitude of about 4,500 ft msl. No comments were recorded during the remainder of the CVR recording to indicate there were any malfunctions with the right side cockpit flight instruments. At 1011:04 severe degradation in CVR audio quality began in all channels, which continued for 3 minutes and 5 seconds. About 1013, at an altitude of about 1,870 ft msl, the pilot and both pilot-rated passengers stated they could see the ground. Although a positive transfer of airplane control was not recorded, subsequent communication between the pilot and right seat passenger was consistent with the pilot having resumed control of the airplane at that time. The pilot requested the flaps be extended at 1013:03, made a right turn to a westerly heading, and requested the landing gear be extended at 1013:22. Subsequent discussions were consistent with the landing gear being configured; however, the gear indicator lights were not illuminated. At 1013:48, the right seat passenger transmitted on the SVH common traffic advisory frequency (CTAF) in part “…we’re having some issues here.” At 1014:05 the rear passenger made a query to the pilot regarding power to the “alternator” (NOTE: the CE-550 airplane is not equipped with an alternator). About 4 seconds later audio quality returned to previous levels on all recorded CVR audio channels. After the audio quality returned, the pilot made a comment indicating that was the “problem”, however, did not specify what the “problem” was or what actions were taken to correct it. There were no additional discussions regarding the pilot’s flight instrumentation for the remainder of the CVR recording. The airplane started a left turn (consistent with the base leg) towards runway 28 about 1014:10, at an altitude of about 1,325 ft and 142 kts groundspeed. The Garmin GTN-750 recordings of airspeed data returned at 1014:12. The GPS data showed the airplane rolled out of the turn onto runway heading about 1014:50, at an altitude of about 1,240 ft msl and 114 kts IAS. Recorded CVR audio indicated the right seat passenger visually acquired the runway and provided directions to the pilot as to where the runway was. About 1015:00, the pilot made comments which indicated he had acquired the runway visually. Recorded data from the GTN-750 showed that the airplane’s airspeed and altitude continued to decrease from the time the airplane was aligned on final approach to the runway until 1015:18, when the airplane was at 984 ft msl and 99 kts IAS. The airplane continued to descend to 942 ft msl until the CVR audio and GPS data ended at 1015:23. The IAS increased to 107 kts and then decreased to about 93 kts during the final five seconds of data. (See figure 1.)
Figure 1: Flight Path Overview with Sequence of Events Accident Site and Wreckage Examination of the accident site revealed that the first identified point of impact (FIPI) was the first (easternmost) light station of the runway 28 Medium Intensity Approach Light System with Runway Alignment Indicator Lights (MALSR), located about 1,380 ft from the runway threshold. Two lightbulbs, the left and fourth from the left position (when viewed looking towards the runway), approximately 6 ft apart, were separated from the otherwise intact 29 ft tall light station (figure 2) and located on the ground near the station. The upper portion of the second MALSR light station located about 180 ft from the FIPI was separated, of which about 15 ft of the frangible pole was still standing. A group of damaged trees located about 235 ft from the FIPI, were sheared about 12 ft above ground level (agl). The first indication of fire was blackened branches and grass near the west side of the trees. A ground impression was observed about 350 ft from the FIPI, near the airport perimeter fence, and extended through the MALSR decision light station. The debris path continued along a westerly heading through the runway overrun to where the main wreckage came to rest on the runway blast area about 400 ft short of the runway 28 threshold, oriented on an easterly heading. Heavy charring of the ground began near the decision light station and continued along the remaining length of the debris field to the wreckage.
Figure 2: First Identified Point of Impact A post impact fire consumed a majority of the fuselage and heat damaged both wings, empennage, and both engines (figure 3). All flight control surfaces were identified in the debris path and main wreckage. No evidence of pre-impact separation of any airplane component or structure was observed.
Figure 3: Aerial view of the accident site. ENGINES Both engines remained attached to the pylon structures and both thrust reversers were found in the stowed position. There was no evidence of uncontained engine failure with either engine. Examination of the cockpit throttle quadrant found both thrust levers to be in the full forward position and both reverse throttle levers in the down position, consistent with being stowed. The No. 1 engine stage 2 low pressure turbine (LPT) blades, viewed through the exhaust duct, were all full length and appeared undamaged. The No. 1 engine fan blades, viewed through the engine inlet, exhibited various degrees of damage and had missing material at the blade tips. The engine inlet surfaces exhibited circumferential scoring between the fan blades forward to the inlet. The No. 2 engine stage 2 LPT blades, viewed through the exhaust duct, were all full length and appeared undamaged. Most of the engine inlet was not attached to the engine. The No. 2 engine fan blades exhibited various degrees of damage and had missing material at the blade tips. Pilot Experience The pilot had type ratings for the A-320, A-330, A-350, B-737, B-757, B-767, CE-500, and DC-10. As part of the pilot’s CE-500 type rating, he had the limitation “CE-500 Second in Command Required.” The pilot reported civil flight experience that included 17,000 total and 400 hours in the last six months as of his last first-class medical application dated April 29, 2025. Review of the right-seat passenger’s logbook indicated that he had 175.3 total flight hours in single engine land airplanes as of November 29, 2025. The right seat passenger’s most recent first-class medical certificate was issued on August 12, 2024. The right seat passenger was not qualified to perform second in command duties per Title 14 CFR part 61.55. The rear passenger reported civil flight experience that included 3,500 total and 65 hours in last six months as of his last medical application dated February 21, 2025. He was issued a second-class medical certificate without limitation. Weather The SVH Automated Weather Observing System (AWOS), recorded on the CVR audio, reported the weather at 0945 as wind calm, visibility 10, ceiling 3,900 ft broken, 4,800 ft overcast, temperature 7° C, dewpoint -0° C, altimeter 30.19. The SVH AWOS, recorded on the CVR audio, reported the weather at 0954 as wind from 050° at 3 knots, visibility 10, 3,900 ft scattered, ceiling 5,000 ft overcast, temperature 7° Celsius, dewpoint 0° C, altimeter 30.19. The Meteorological Aerodrome Report (METAR), at 1015, reported weather at SVH as: wind calm, visibility of 5 statute miles, heavy drizzle, ceiling broken at 1,200 ft agl, ceiling broken at 2,200 ft agl, overcast clouds at 5,000 ft agl, temperature of 7°C, dew point temperature of 1°C, altimeter setting of 30.19 inHg; Remarks: station with a precipitation discriminator, temperature of 7.2°C and dew point temperature of 1.0°C. Recorders The airplane was equipped with a Fairchild GA-100 tape-based cockpit voice recorder (CVR). The CVR was recovered at the accident site by NTSB personnel. Audio recording of the accident flight was successfully downloaded from the CVR. The recorder contained about 31 minutes of analog audio on a continuous loop tape in a four-channel format: one channel for each flight crew and one channel for the cockpit area microphone (CAM) with one spare channel. Audio quality of the recording was poor with low signal-to-noise ratio and extraordinary means were required to make portions of the recording intelligible. The airplane was not equipped with a flight data recorder, nor was it required to be. A Garmin GTN-750 was recovered at the accident site by NTSB personnel. The GTN-750 is a combination GPS/Navigation receiver/Radio/Multi-Function display that has the capability of recording some data in non-volatile memory. In its configuration on the accident aircraft the unit recorded about 20 parameters for the full accident flight.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
Wikipedia article: 2025 North Carolina Cessna Citation II crash
- Revision
- 1372037990 · 2026-08-30 · retrieved 2026-09-18
- Wikidata
- Q137454501
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record WPR26MA063
- Event ID
- 20251218202182
- Case number
- WPR26MA063
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
- Record
- Wikipedia article "2025 North Carolina Cessna Citation II crash" (page 81871726, revision 1372037990); merged with NTSB case WPR26MA063 (events / aircraft)
- Date
- NTSB record WPR26MA063: NTSB API eventDate, eventTimeUtc and eventTimeUtcOffsetHours (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record WPR26MA063
- Map position
- NTSB record WPR26MA063: events decimal coordinates
- Aircraft, operator and route
- NTSB record WPR26MA063: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record WPR26MA063: operated under Part 91: General Aviation
- Fatalities
- NTSB record WPR26MA063: NTSB API totalFatal
- Ground fatalities
- NTSB record WPR26MA063: events.inj_f_grnd
- Summary
- Wikipedia infobox: summary
Source notes (4)
- One occurrence in two sources, merged: the Wikipedia article "2025 North Carolina Cessna Citation II crash" and NTSB case WPR26MA063, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- 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.
- Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states the airplane "was destroyed when it was involved in an accident".