ORLICAN S R O M-8 EAGLE near St. Louis, MO — 2022-12-05
- Date
- 2022-12-05
- Location
- St. Louis, MO, USA
- Airport
- 1H0
- Aircraft
- ORLICAN S R O M-8 EAGLE
- Registration
- N602TG
- Category
- Airplane
- Highest injury
- Minor
- Fatalities
- 0
- Phase of flight
- Approach
Probable cause
The pilot’s failure to maintain adequate airspeed/angle-of-attack during the landing approach, which resulted in an aerodynamic stall and hard landing.
NTSB narrative
According to the pilot and pilot-rated passenger, they performed one traffic pattern takeoff and landing before departing to a practice area with no issues noted while in the traffic pattern. After arriving to the practice area, the pilot initiated a climb and noted a caution indication for the right cylinder head temperature. The pilot reduced engine rpm and descended, and the cylinder temperatures again indicated normal. The pilot added full power to initiate a climb again and he reported that the engine “stuttered.” The pilot reduced the engine rpm; the engine operated without issue and the pilot added full power again. The pilot reported engine “stuttered” again and the stuttering continued when the rpms were reduced. The pilot elected to return to the airport, where the ground visibility was reducing due to dusk light conditions. The pilot reported that during the return flight to the airport the airplane was struggling to maintain altitude and that he had to fly nose-up to keep from descending. The pilot reported the engine continued to operate in a rough condition. About 20 ft above runway 16, the airplane began to sink, and the pilot added engine power. He stated the engine did not respond, and “we just fell.” The airplane impacted the runway, veered to the right, and nosed over. The pilot and passenger attempted to secure the airplane’s systems and extricated themselves from the airplane. The recorded flight and engine data revealed no anomalies consistent with what the pilot reported had occurred during the accident flight. Examination of the airframe and engine did not reveal any preimpact mechanical malfunctions or failures that would have precluded normal operation. Based on the evidence and available flight data, it is likely that the pilot failed to fly the airplane at the appropriate airspeed/angle-of-attack during the landing approach, which resulted in an aerodynamic stall and hard landing.
Analysis
- Primary failure mode
- Engine power loss
- First missed decision gate
- Pilot could have aborted the approach earlier due to engine issues.
NTSB coding
Evidence available
- Photos
- 11 docket documents
Docket documents11
- PILOT/OPERATOR AIRCRAFT ACCIDENT REPORT, NTSB FORM 6120.1form
- PILOT/OPERATOR AIRCRAFT ACCIDENT REPORT, NTSB FORM 6120.1 - PASSENGERform
- EMAIL CORRESPONDENCE - DYNON/ROTAX/NTSBother
- EMAIL CORRESPONDENCE - ORLICAN - SIMULATION AND ANALYSISother
- PILOT'S OPERATING HANDBOOK - EXCERPT OF AIRSPEED LIMITATIONSother
- RECORD OF CONVERSATION - ROTAX ENGINES - ENGINE EXAMINATIONother
- X-PLANE SIMULATION - PRODUCED BY ORLICANother
- ACCIDENT PHOTOGRAPHSphotos
- ATTACHMENT 1 TO EFIS - SPECIALIST'S FACTUAL REPORT_TABULAR DATAreport
- ATTACHMENT 2 TO EFIS - SPECIALIST'S FACTUAL REPORT_ALERT DATAreport
- EFIS - SPECIALIST'S FACTUAL REPORTreport
Related mishaps
- CESSNA 170B
2025-08-23 · Livermore Falls, ME
- SCHWEIZER SGS 1-26B
2025-04-26 · Ontario, OR
- LET L 33 SOLO
2024-09-01 · Kingman, KS
- CESSNA 177B
2024-09-01 · Shell Knob, MO
- GLASFLUGEL STANDARD LIBELLE
2024-07-25 · Fields, OR
- SCHWEIZER SGS 1-26E
2023-04-15 · Wake Forest, NC