OpenAirDocs.org

20240322003139I

Incident · Minor damage
Open the Markdown

FAA incident report · Czech Sport Aircraft A S SPORTCRUISER · Woods Cross, UT · March 22, 2024

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
March 22, 2024 · 11:10 local
Place
Woods Cross, UT
Airport
Skypark
Phase of flight
Landing: Touchdown
Operating rules
Pilot school (Part 141)
Operator
BF1S
Damage
Minor damage
Aircraft
N135BF
Reported as
Czech Sport Aircraft A S Sportcruiser
Reported engine
ROTAX 912ULS series
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificates
Commercial pilot, flight instructor, private pilot
Pilot’s flight hours
780 total200 in this make and model101 in the last 90 days
N135BFRegistered now · Czech Sport Aircraft A S SPORTCRUISERS/N C0621 · Built 2017Airframe modelCzech Sport Aircraft A S SPORTCRUISEREngine modelRotax 912ULS series4 cycle

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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.

As the FAA filed it

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.