CEN24FA064 · Pilatus PC-12/45
Pilatus PC-12/45 · Accident: collision with terrain/object (non-CFIT) on approach
From Jacksonville Executive at Craig Airport (CRG) to San Angelo Regional Mathis Field (SJT)
Event
- NTSB case
- CEN24FA064
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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
Pilatus PC-12/45
- Aircraft type
- Pilatus PC-12
- 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
- N188PC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jacksonville Executive at Craig Airport (CRG), Jacksonville, FLTo San Angelo Regional Mathis Field (SJT), San Angelo, TX
- Aircraft age
- About 26 years (built 1997)
- 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
- Approach · IFR missed approach
- 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
- Collision with terrain/object (non-CFIT)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Psychological
- 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
On December 14, 2023, about 1218 central standard time (CST), a Pilatus PC-12/45, N188PC, was destroyed when it was involved in an accident near Christoval, Texas. The pilot, one passenger, and three pets were fatally injured. The flight was conducted under 14 Code of Federal Regulations Part 91 as a personal flight. Federal Aviation Administration (FAA) air traffic control (ATC) recordings and automatic dependent surveillance – broadcast (ADS-B) data revealed that the airplane had departed Jacksonville Executive at Craig Airport (CRG), Jacksonville, Florida, about 0751 CST, and was en route to San Angelo Regional Airport (SJT), San Angelo, Texas. The pilot was receiving radar vectors for the RNAV (GPS) runway 36 approach to SJT and was level about 4,300 ft mean sea level (msl). About 1211, the pilot reported to ATC that the tops of the clouds were variable between 4,100 ft and 4,400 ft msl. At 12:17:24, ATC stated, “turn right heading 030 maintain 4,300 [ft msl] until established on the final approach course, cleared RNAV 36 approach” At 12:17:32, the flight track passed through the final approach course and continued a shallow right turn At 12:17:36, the pilot stated “we overshot it” At 12:17:39, ATC stated “I know that’s why a gave you a 030” At 12:17:40, the flight track began a right descending turn about 1,000 fpm At 12:17:44, the descent rate was about 5,000 fpm and the right turn steepened At 12:17:47, the pilot stated “we got a problem” and was the final recorded transmission from the accident airplane At 12:17:49, the flight track continued in a steep right turn with a descent rate about 15,000 fpm
Figure 1. Google Earth view of the accident area with the ADS-B flight track, the RNAV (GPS) runway 36 initial approach fix “DBASE”, and the 002° final approach course. The airplane impacted trees and terrain about 15 miles south of SJT and the wreckage debris was aligned on a 100° magnetic heading. The initial impact point was defined by a small tree that was cut at a 24° angle slanted down toward south and surrounded by small wreckage debris, which included pieces of the right wing tip and a green navigation light. The initial ground impact crater was immediately adjacent to the tree, measured about 1 ft deep by 20 ft long, and contained a lot of small wreckage debris and one propeller blade. The main wreckage was located about 500 ft to the east of the initial impact area. A large section of the left wing remained mostly intact and was found on the right side of the debris field near the main wreckage. The area between the initial impact and the main wreckage contained a significant amount of airplane parts and wreckage debris. The main portion of the engine was located about 870 ft from the initial impact area. The farthest piece of wreckage was a main landing gear tire that was located about 1,320 ft from the initial impact. Several portions of the wreckage sustained thermal damage and contained black soot. The engine components exhibited torsional deformation and rotational signatures. The propeller impact-separated from the engine with the propeller shaft and associated reduction gearbox bearings still attached. The cylinder, piston, and feathering spring assembly impact-separated from the propeller hub and were found near the propeller assembly about 50 ft from the engine. The propeller assembly and two blades remained attached and two of the four blades impact-separated from the propeller assembly. One blade fractured from the blade retention pocket and was found in the initial impact crater. The other blade fractured at the shank and was found just east of the initial impact crater in the debris field. All four blades exhibited chordwise rotational scoring, leading edge gouges, and compound bend and twist signatures.
Figure 2. Aerial image of the accident site facing east. The initial impact area, main wreckage, and end of the wreckage debris field are labeled in red. The archived meteorological information and the accident pilot’s report to ATC revealed that the airplane was likely in instrument meteorological conditions (IMC) during the approach. There was potential for turbulence in clouds, no icing below 11,000 ft, and no significant precipitation noted. Maintenance records revealed that the airplane had undergone an annual inspection which was completed on November 22, 2023, at aircraft total time 3,990.1 hours. The pilot’s electronic flight logbook revealed that in the last year he had accumulated about 111 hours in the accident airplane, of which 16.3 hours were logged in actual IMC. In 2020, the airplane was upgraded with Garmin avionics and components that included two Garmin G600TXi touchscreen flight displays, two Garmin GTN750Xi flight navigators, a Garmin GI275 electronic attitude indicator, and a Garmin GMC 605 autopilot controller. These devices were located in the wreckage and were sent to the NTSB Vehicle Recorders Laboratory for examination and data extraction. The wreckage was retained for further examination and testing.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN24FA064
- Event ID
- 20231214193525
- Case number
- CEN24FA064
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
- 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: 76dbdf1e0bb727d8cd4ae4d6678a7f86ec323824ee52e99f1dc06a4c917ad03b; retrieved 2026-09-15T08:09:18.823Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states the airplane was destroyed and describes an extensive fragmented debris field.