# Accident 20240407005349A: Cessna 208, Ellington, CT, April 7, 2024 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: April 7, 2024, 10:25 local time - Place: Ellington, CT - Airport: Ellington - Damage: Substantial damage - Phase of flight: Landing: Touchdown - Operating rules: General operating rules (Part 91) - Location: 41.9254° N, 72.4571° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=41.9254&lon=-72.4571&mi=10 - Aircraft: N90JF, registered now (https://openairdocs.org/aircraft/N90JF) (OpenAirDocs) - Registry model: Cessna 208 (registry code 2073702, https://openairdocs.org/model/cessna-208) (OpenAirDocs) - Registry engine: Pratt & Whitney Canada PT6A-114A (registry code 52257, https://openairdocs.org/engine/pratt-whitney-canada-pt6a-114a) (OpenAirDocs) - Reported make and model: CESSNA 208 - Reported engine: P&W CANADA PT6A-114A - People aboard: 7 - Fatal injuries: 0 - Other injuries: 1 - Pilot certificates: Commercial pilot - Pilot flight hours: 865 total, 204 in this make and model, 204 in the last 90 days - NTSB investigation: [NTSB ERA24LA168](https://openairdocs.org/ntsb/ERA24LA168) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20240407005349A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON 7 APRIL 2024, AT 1520(Z) THE FAA RECEIVED NOTICE REGARDING AN ACCIDENT IN ELLINGTON, CONNECTICUT, A CESSNA 208 LANDED ON A BERM SHORT OF RUNWAY 01 FOR UNKNOWN REASONS. 7 PERSONS ON BOARD, NO INJURIES, AND AIRCRAFT DAMAGE EXTENT UNKNOWN. THIS FAA FEDERAL AVIATION ADMINISTRATION (FAA) IIC (INVESTIGATOR IN CHARGE) AND AN ADDITIONAL ASI (AVIATION SAFETY INSPECTOR) ARRIVED AT THE ACCIDENT SCENE AT ELLINGTON AIRPORT (7B9) AT 12:52 LOCAL TIME. THE INITIAL SCENE HAD A STATE POLICE TROOPER MONITORING A SECURED AREA. A CURSORY EXAMINATION OF THE ACCIDENT AREA AND AIRCRAFT BY FAA PERSONNEL WAS CONDUCTED AT THIS TIME. THE AIRCRAFT WAS IN THE GRASS STRIP BETWEEN THE RUNWAY AND THE TAXI/PARKING AREA, 12 FEET FROM THE RIGHT EDGE OF THE RUNWAY PAVEMENT, AND 58 FEET FROM THE BEGINNING OF RUNWAY 01. THE AIRCRAFT WAS NOTED TO BE LARGELY INTACT, AND WAS POINTING AT A HEADING OF APPROXIMATELY 46 DEGREES. THERE WAS NO EVIDENCE OF PRE- OR POST-IMPACT FIRE. THE LOWER NOSE AREA OF THE AIRCRAFT WAS PARTIALLY DUG INTO THE GROUND, WITH MODERATE DAMAGE TO THE LOWER NOSE FAIRING SECTION, EXHAUST, GEAR TRUNNION, AND PROPELLER. THE NOSE GEAR ASSEMBLY WAS NOT ATTACHED, WITH NO OTHER OBVIOUS AIRCRAFT STRUCTURES OR COMPONENTS MISSING. ALL THREE PROPELLER BLADES TIPS WERE BENT REARWARDS, IN A COUNTERCLOCKWISE DIRECTION, (FROM PIC PERSPECTIVE) INDICATIVE OF ROTATION WHEN THE BLADES CONTACTED. THE LOWER NOSE GEAR ASSEMBLY WAS LOCATED IN THE GRASS ON THE LEFT SIDE OF THE RUNWAY, APPROXIMATELY 43FT AWAY FROM THE AIRCRAFT IN A WEST-SOUTHWEST DIRECTION. IT HAD SEVERE PISTON/CYLINDER DAMAGE, WITH THE AND TIRE AND RIM STILL INTACT. THE RUNWAY DIRECTLY SOUTH ALONG THE IMPACT PATH HAD SOIL AND ROCK DEBRIS THROUGHOUT, ALONG WITH SCRAPE MARKS LEADING TO THE ACCIDENT SCENE. LEADING AWAY FROM THE RUNWAY INTO THE GRASS IN A SOUTHERLY DIRECTION, FURROWED SOIL, ADDITIONAL NOSE GEAR PARTS AND A LINE OF 11 PROP STRIKE MARKS, APPROXIMATELY 12 INCHES ON CENTER WERE NOTED. FURTHER SOUTH WAS NOTED A GULLEY WITH A STREAM AT THE BOTTOM, RUNNING ROUGHLY EAST/WEST. CONTINUING SOUTH INTO A FIELD WAS A BERM ROUGHLY 3 FEET HIGH, ADJACENT TO THE SOUTH SIDE OF THE STREAM, RUNNING ROUGHLY EAST/WEST AND PERPENDICULAR TO THE RUNWAY DIRECTION. IMPACT MARKS WERE NOTED ON THE SOUTHERN SIDE OF THE BERM FROM ALL THREE LANDING GEAR. DIRECTLY SOUTH OF THE BERM, TIRE MARKS WERE NOTED IN THE FIELD INDICATIVE OF ALL THREE GEAR CONTACTING THE GROUND, AND WERE MEASURED AT 106 FEET BEFORE THE BEGINNING OF THE RUNWAY. (AS MEASURED FROM THE FARTHEST MAIN LANDING GEAR MARK.) MULTIPLE PASSENGERS INTERVIEWED STATED THEY HEARD A STALL ALARM JUST BEFORE OR DURING THE IMPACT/TOUCHDOWN. ONE PASSENGER STATED THAT THEY COULD TELL THE APPROACH WAS LOWER THAN PREVIOUS FLIGHTS BECAUSE OF THE LOCATION OF THE SOUTHERN TREE LINE BRANCHES, AS SEEN THROUGH THE WINDOW IN THE AFT OF THE AIRCRAFT. THE PIC STATED HE WAS FLYING THE ACCIDENT AIRCRAFT WHEN HE “CAME UP LANDING SHORT OF THE RUNWAY, BREAKING THE MAIN LANDING GEAR.” ## The NTSB's investigation of this event (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB ERA24LA168](https://openairdocs.org/ntsb/ERA24LA168), Apr 7, 2024: Cessna 208 (N90JF), Ellington, CT, substantial damage. Probable cause: The pilot’s failure to maintain a proper glidepath to the runway, which resulted in a runway undershoot and collision with terrain. ## Other reports on N90JF (1) Matched to the same aircraft by N-number and date. - [Accident 20220604009539A](https://openairdocs.org/incident/20220604009539A), Jun 4, 2022: Cessna 208 (N90JF), Ellington, CT, Substantial damage. Mishap pilot stated that the mishap aircraft suffered engine failure / power loss while in descent attitude. Mishap pilot was unable to restart the engine and… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.