CEN25FA148 · Anusiewicz CASSUTT III M
Anusiewicz CASSUTT III M · Accident: abrupt maneuver on approach
From Haskell Airport (2K9) to an unrecorded destination
Event
- NTSB case
- CEN25FA148
- 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
- API-reported fatalities
- 1 · 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
- Visual Meteorological Cond
Anusiewicz CASSUTT III M
- Aircraft type
- Anusiewicz CASSUTT
- 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
- N5RR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Haskell Airport (2K9), Haskell, OKTo not recorded
- Aircraft age
- About 51 years (built 1974)
- 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 · VFR pattern downwind
- 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
- Abrupt maneuver
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On April 8, 2025, about 1459 central daylight time, a Cassutt III M airplane, N5RR, was substantially damaged when it was involved in an accident near Haskell, Oklahoma. The pilot was fatally injured. The aircraft was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. A witness stated that he was standing in front of the accident pilot’s hangar and had observed the pilot complete two or three laps around the airport traffic pattern. On the final lap, he said the pilot flew the length of the runway at about 100 feet above the ground and then saw the airplane pitch nose up steeply off the end of the runway. The airplane climbed until the airplane slowed down, at which point the airplane leveled off and turned through crosswind to the downwind leg of the traffic pattern where it began to pick up speed once again. He stated that the pilot had routinely done this maneuver in the past. The witness stated that while the airplane was on the downwind leg of the traffic pattern, it entered an aileron roll, and while upside down, the nose dipped towards the ground and the airplane began to lose altitude. The airplane continued through the roll, and it looked like the pilot had managed to level the wings of the airplane and was in the process of pulling out of the ensuing shallow dive but didn’t have enough altitude to do so. The airplane impacted the ground at a shallow angle, bounced and tumbled with components separating from the airplane. According to the witness, it all happened in about 5 seconds and that it occurred very fast. The witness stated that he had never seen the pilot perform any aerobatic type maneuvers in the past. Multiple witnesses stated that the engine was running at full power at the time of the accident and heard no indication of an engine issue. The airplane was examined at the accident site, and all major components of the airplane were present. Control cable continuity was verified, and no flight control anomalies were noted. The engine exhibited impact damage and no anomalies were noted. Wood propeller blade fragments were found on and in the ground at the initial point of impact. The propeller hub remained attached to the propeller mounting flange. The pilot’s cellphone was recovered at the accident site, and a cursory examination of the phone provided flight track data from an application installed on the phone. No phone calls or texts were present at the time of the accident. The phone was retained for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN25FA148
- Event ID
- 20250408199980
- Case number
- CEN25FA148
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- 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. 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: 5b6a1d437432bed3ae90a190b881a164546f89f59f9704ef0d99ac9e1af64ba6; retrieved 2026-09-15T09:03:43.297Z.