# Incident 20250924015239I: Fx Consulting Ltd EVOLUTION, Madras, OR, September 24, 2025

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 24, 2025, 10:50 local time
- Place: Madras, OR
- Airport: Madras Municipal
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 44.6702° N, 121.1551° W: Placed by OpenAirDocs at MADRAS MUNI (S33), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.6702&lon=-121.1551&mi=10
- Aircraft: N167FX, registered now (https://openairdocs.org/aircraft/N167FX) (OpenAirDocs)
- Registry model: FX Consulting EVOLUTION (registry code 056379X, https://openairdocs.org/model/fx-consulting-evolution) (OpenAirDocs)
- Registry engine: Pratt & Whitney Canada PT6A-140AG (registry code 51800, https://openairdocs.org/engine/pratt-whitney-canada-pt6a-140ag) (OpenAirDocs)
- Reported make and model: FX CONSULTING LTD EVOLUTION
- Reported engine: P&W CANADA PT6A-140AG
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 1,605 total, 303 in this make and model, 60 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20250924015239I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

THE PILOT IN COMMAND WAS PERFORMING A SIMULATED ENGINE OUT LANDING WITH A SAFETY PILOT. THE PILOT FLEW TO THE “HIGH KEY” LOCATION AT S33, DESCENDED TO THE “LOW KEY”, THEN FLEW THE APPROACH TO RUNWAY 16 AND LANDED AS IF THE ENGINE WAS OFF.  IN THIS SITUATION, THE PROPELLER WAS NOT FEATHERED, AND THE POWER CONTROL WAS SET TO IDLE PRODUCING ROUGHLY 120 FT. POUNDS OF TORQUE TO SIMULATE “ENGINE OUT, FEATHERED”. THE PILOT'S STATED TYPICAL LANDING IS AT 200 FT. LBS, PULLING THE POWER CONTROL BACK TO IDLE IN FLARE. UPON FLARE OF THE SIMULATED ENGINE OUT LANDING THE PILOT PULLED BACK ON THE POWER CONTROL AS NORMAL TO SET FOR IDLE. WHEN THE POWER CONTROL DID NOT MOVE, HE GRIPPED HARDER AND UNINTENTIONALLY ACTIVATED THE SAFETY MECHANISM ALLOWING THE POWER CONTROL TO MOVE INTO BETA WHILE STILL IN FLARE. IMMEDIATELY, THE AIRCRAFT FELL OUT OF FLARE TO THE RUNWAY LANDING HARD CAUSING THE NOSE GEAR BOTTOM THIRD TO BREAK AWAY FROM THE NOSE STRUT. THEN CAUSING THE PROPELLER TO STRIKE THE RUNWAY. THE PILOT MAINTAINED CONTROL OF THE AIRCRAFT DOWN THE CENTERLINE LIGHTLY APPLYING BREAKS AND USING FRICTION TO REDUCE SPEED. THE PILOT WAS ABLE TO TURN THE AIRCRAFT OFF THE RUNWAY AT THE FIRST TAXIWAY ENTRANCE COMING TO A STOP JUST OFF THE RUNWAY.

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.