# Accident 20260518009089A: Cessna 172N, Westerly, RI, May 18, 2026 - Type: FAA accident report (Accident/Incident Data System), as reported - Date: May 18, 2026, 12:02 local time - Place: Westerly, RI - Airport: Westerly State - Damage: Destroyed - Phase of flight: Landing: Approach - Operating rules: General operating rules (Part 91) - Location: 41.3535° N, 71.8105° W: From the FAA - Nearby events: https://openairdocs.org/map.md?lat=41.3535&lon=-71.8105&mi=10 - Aircraft: N733CP, registered now (https://openairdocs.org/aircraft/N733CP) (OpenAirDocs) - Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs) - Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs) - Reported make and model: CESSNA 172N - Reported engine: LYCOMING 0-320 SERIES - People aboard: 1 - Fatal injuries: 1 - Other injuries: 0 - Pilot certificates: Commercial pilot, flight instructor - NTSB investigation: [NTSB CEN26FA192](https://openairdocs.org/ntsb/CEN26FA192) (OpenAirDocs) - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/20260518009089A ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. ON MAY 18TH 2026 A CESSNA 172 CRASHED LANDED IN A FIELD NORTHWEST FROM WESTERLY AIRPORT (WST) OFF THE APPROACH END OF RUNWAY 14. THE SOLE OCCUPANT ON BOARD SUFFERED FATAL INJURIES. THE DESCENT TO THE CRASH ZONE WAS WITNESSED BY SEVERAL BYSTANDERS AS WELL AS A WESTERLY POLICE DEPARTMENT OFFICER ON DUTY. THE OFFICER CALLED THE EMERGENCY INTO THE DISPATCH CENTER AND PROCEEDED TO THE CRASH SITE. UPON ARRIVING AT THE CRASH SITE THE OFFICER NOTED THAT THE AIRCRAFT WAS NOT RUNNING, FUEL WAS LEAKING DOWN THE LEFT WING OF THE AIRCRAFT, AND THERE WAS NO FIRE SEEN. THE OFFICER WAS ABLE TO LIFT THE UNRESPONSIVE OCCUPANT OUT OF THE PILOT SEAT OF THE AIRCRAFT WHO WAS NOTED NOT TO BE RESTRAINED BY A LAP OR SHOULDER BELTS. THE OFFICER NOTED SIGNIFICANT INJURY TO BOTH LEGS, CHEST, NECK, AND HEAD OF THE INDIVIDUAL. MINOR INJURIES TO THE HANDS AND ARMS WERE ALSO NOTED. OFFICER IMMEDIATELY STARTED LIFE SAVING MEASURES, OCCUPANT WAS TRANSPORTED TO WESTERLY HOSPITAL. AIRCRAFT AND SITE WERE THEN SECURED BY WESTERLY POLICE AND FIRE DEPARTMENTS. THE SCENE OF THE CRASH WAS LOCATED ON THE NORTHERN PART OF A FARM FIELD NEAR A TREE LINE. INITIAL IMPRESSION OF THE AIRCRAFT SHOWED TYPICAL SIGNS OF A HIGH ANGLE/HIGH RATE OF SPEED IMPACT. DEBRIS FIELD WAS LOCAL TO THE AREA OF IMPACT WITH SEVERAL GROUND SCAR SIGNATURES TO THE AIRCRAFT’S SOUTHWEST. MOST OF THE AIRCRAFT’S COMPONENTS WERE LOCATED AT FINAL RESTING PLACE EXCLUDING THE RIGHT-WING TIP, PART OF THE TAIL SKIN, AND THE RIGHT-SIDE WHEEL WHICH WERE IN THE VICINITY. THE ENGINE COMPARTMENT WAS COMPRESSED INWARD TOWARD THE PILOT/PASSENGER SEATS WITH THE TAIL BROKEN OFF TO THE RIGHT SIDE OF THE AIRFRAME. LEFT WING WAS LEADING FORWARD, BREAKING AT THE AFT ATTACHMENTS. LEFT WING FUEL TANK WAS FOUND EMPTY, BUT IT IS NOTED THAT THIS WAS THE SIDE THE OFFICERS STATED WAS LEAKING FUEL. RIGHT WING SHIFTED ENTIRELY FORWARD BREAKING / BENDING AT THE CONNECTION POINTS OF THE FUSELAGE. THE FUEL TANK HAD FUEL UPON INSPECTION. THE CONTROL CABLES WERE FOUND IN TACT WITH THE EXCEPTION OF THE RIGHT AILERON CABLE. THE RIGHT AILERON CABLE WAS SNAPPED AND CORROSION WAS NOTED AT THE BREAKING POINT. THE CABLE SNAPPED AT THE LOCATION THAT WOULD BE RUNNING THROUGH THE LOWER TURNBUCKLE UNDER THE FLOOR OF THE CABIN INTERIOR. INTERVIEW WITH THE OWNER YIELDED THAT THE PRIMARY PURPOSE OF THE AIRCRAFT WAS FLIGHT INSTRUCTION AND THE OCCUPANT ON BOARD WAS AN EMPLOYED CERTIFIED FLIGHT INSTRUCTOR. THE PURPOSE OF THIS FLIGHT WAS TO CHECK AN AMPERAGE GAUGE WHICH HAD BEEN GIVING ERRATIC READINGS IN PAST FLIGHTS. INTERVIEW WITH MECHANIC CONFIRMED THAT THIS WAS THE PURPOSE OF THE FLIGHT AND THAT THE AIRCRAFT WAS BEING MAINTAINED AT THEIR SHOP FOR THIS ISSUE. THE PROBLEM WAS UNABLE TO BE DUPLICATED BY THE MECHANIC AND THUS RETURNED TO SERVICE BACK TO THE OPERATOR TO DETERMINE IF THE PROBLEM STILL EXISTED, THIS WAS TO BE TESTED BY FLYING THE AIRCRAFT AROUND THE PATTERN ONCE OR TWICE. THE APPROACH OF THE AIRCRAFT WAS CAPTURED ON VIDEO BY A LOCAL RESIDENT AND A BUSINESS. THE AIRCRAFT APPEARS TO TURN FINAL FOR RUNWAY 14. AN OBJECT WAS NOTED AS FLYING IN THE AREA OF THE RUNWAY 14 FINAL IN ADDITION TO THE AIRCRAFT. AFTER ALIGNING WITH THE RUNWAY, THE OBJECT APPEARED TO MOVE TOWARDS THE AIRCRAFT. THE AIRCRAFT BEGAN A PITCH UP AND RIGHT TURN. THE RIGHT TURN CONTINUED INTO A STEEP DESCENT BEFORE DISAPPEARING OFF THE CAMERAS AS THE AIRCRAFT IMPACTED THE FIELD. THE LAST FRAMES OF THE VIDEO SHOW THE AIRCRAFT IN A VERY STEEP NOSE DOWN ATTITUDE. ## 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 CEN26FA192](https://openairdocs.org/ntsb/CEN26FA192), May 18, 2026: Cessna 172N (N733CP), Westerly, RI, substantial damage, 1 fatal, investigation ongoing ## Other reports on N733CP (3) Matched to the same aircraft by N-number and date. - [Incident 19880815040649I](https://openairdocs.org/incident/19880815040649I), Aug 15, 1988: Cessna 172N (N733CP), Ft Meade, MD, Minor damage. Aircraft tipped up on its nose by a strong gust of wind while taxiing to park. Had surface winds to 66KTS in area. - [Accident 19860914047659A](https://openairdocs.org/incident/19860914047659A), Sep 14, 1986: Cessna 172N (N733CP), Seven Springs, PA, Substantial damage. Approach high. Bounced. Aborted a go around attempt after wing tip and left gear contacted the ground. - [Accident 19811130077059A](https://openairdocs.org/incident/19811130077059A), Nov 30, 1981: Cessna 172N (N733CP), Stevensville, MD, Substantial damage. Lost directional control in crosswind landing. Rolled off side of runway into a ditch. 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.