# Incident 20240322003139I: Czech Sport Aircraft A S SPORTCRUISER, Woods Cross, UT, March 22, 2024

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 22, 2024, 11:10 local time
- Place: Woods Cross, UT
- Airport: Skypark
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: Pilot school (Part 141)
- Operator: BF1S
- Location: 40.8681° N, 111.9275° W: Placed by OpenAirDocs at SKYPARK (BTF), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.8681&lon=-111.9275&mi=10
- Aircraft: N135BF, registered now (https://openairdocs.org/aircraft/N135BF) (OpenAirDocs)
- Registry model: Czech Sport Aircraft A S SPORTCRUISER (registry code 0600066, https://openairdocs.org/model/czech-sport-aircraft-a-s-sportcruiser) (OpenAirDocs)
- Registry engine: Rotax 912ULS series (registry code 55572, https://openairdocs.org/engine/rotax-912uls-series) (OpenAirDocs)
- Reported make and model: CZECH SPORT AIRCRAFT A S SPORTCRUISER
- Reported engine: ROTAX 912ULS SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, private pilot
- Pilot flight hours: 780 total, 200 in this make and model, 101 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20240322003139I

## Narrative

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

ON MARCH 22, 2024, THE PILOT IN COMMAND (PIC) OF THE AIRCRAFT DEPARTED BTF AT 1037 MST ON RUNWAY 17 WITH THE INTENT OF PROVIDING TAKEOFF AND LANDING DEMONSTRATIONS TO A STUDENT PILOT.  THE DURATION OF THE FLIGHT WAS FLOWN IN CLOSE PROXIMITY TO BTF AND WAS UNEVENTFUL.  WHILE ON FINAL APPROACH FOR RUNWAY 17, THE PIC IDENTIFIED A HELICOPTER THAT APPEARED TO BE MIDFIELD TO THE EAST OF RUNWAY 17.  THE PIC STATED THAT THEY BELIEVED THE HELICOPTER TO BE TAKING OFF ON RUNWAY 35 BRINGING THEM INTO THEIR LANDING PATH.  THEY ELECTED TO CONTINUE LANDING; HOWEVER, THEY HAD MAINTAINED TOO MUCH SPEED AND DURING TOUCH DOWN THE AIRCRAFT BEGAN TO PORPOISE.  AT THIS POINT THE PIC LOST CONTROL AND DEPART THE RUNWAY INTO THE FIELD DIRECTLY WEST OF THE RUNWAY.  THESE ACTIONS CAUSED THE NOSE LANDING GEAR TO SEPARATE FROM THE AIRCRAFT AS WELL AS CAUSED MINOR DAMAGE TO SHEET METAL AND OTHER COMPONENTS.  ADSB DATA SHOWED THE SUSPECTED HELICOPTER HAD NOT ENCROACHED ON THE LANDING PATH AND A WRITTEN STATEMENT FROM THE PIC SUBMITTED ON MARCH 22 CONCLUDED THAT THEY MISS PERCEIVED THE HELICOPTER’S TRUE LOCATION AND THREAT LEVEL.

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.