# Incident 20240228001649I: Socata TBM 700, Broomfield, CO, February 28, 2024

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 28, 2024, 15:30 local time
- Place: Broomfield, CO
- Airport: Rocky Mountain Metropolitan Ai
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 39.9088° N, 105.1170° W: Placed by OpenAirDocs at Rocky Mountain Metropolitan Airport (BJC), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.9088&lon=-105.1170&mi=10
- Aircraft: N661EK, registered now (https://openairdocs.org/aircraft/N661EK) (OpenAirDocs)
- Registry model: Socata TBM 700 (registry code 8682000, https://openairdocs.org/model/socata-tbm-700) (OpenAirDocs)
- Registry engine: Pratt & Whitney PT6A series (registry code 52032, https://openairdocs.org/engine/pratt-whitney-pt6a-series) (OpenAirDocs)
- Reported make and model: SOCATA TBM 700
- Reported engine: P&W PT6A SER
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, private pilot, student
- Pilot flight hours: 1,550 total, 300 in this make and model, 30 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20240228001649I

## Narrative

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

ON FEB 28, 2024 AT APPROXIMATELY 1530 MST THE AIRCRAFT WAS THE SUBJECT OF AN INCIDENT WHILE LANDING ON RWY 30R AT BJC.  AS THE AIRCRAFT MADE CONTACT WITH THE RUNWAY, THE PILOT NOTED SCRAPING SOUNDS AND SUCCESSFULLY INITIATED A ‘GO-AROUND’, EXTENDED THE LANDING GEAR AND LANDED WITHOUT FURTHER INCIDENT.  THE PILOT ADMITTED THAT WHILE PERFORMING THE ‘BEFORE LANDING CHECKLIST’, HE BECAME DISTRACTED WHEN HE WAS NOTIFIED OF SEVERE TURBULENCE BEFORE SWITCHING BETWEEN RADIO FREQUENCIES AND HE FAILED TO EXTEND THE LANDING GEAR.   HE STATED THAT THE FLAPS WERE IN THE ‘TAKE OFF’ POSITION DUE TO ANTICIPATED TURBULENCE, WHICH INHIBITED WARNINGS AND HE DOES NOT RECALL HEARING OR SEEING ANY WARNINGS RELATED TO THE LANDING GEAR NOT BEING EXTENDED.  THERE WERE NO KNOWN, OR SUSPECTED, MAINTENANCE ISSUES WITH THE AIRCRAFT PRIOR TO THIS INCIDENT.  MINOR DAMAGE WAS SUSTAINED TO THE TIPS OF THE PROPELLER BLADES, ALL LOWER ANTENNAE’S AND BOTH LOWER AFT FUSELAGE STRAKES.

THERE WERE TWO PASSENGERS ONBOARD AND NO INJURIES REPORTED.  THE AIRCRAFT TAXIED TO A NEARBY HANGAR AND IS CURRENTLY AWAITING REPAIRS.  THE INCIDENT WAS REPORTED THE FOLLOWING DAY (FEB 29, 2024) BY AN EYEWITNESS TO BJC AIRFIELD OPERATIONS WHO NOTIFIED THE FAA’S REGIONAL OPERATIONS CENTER.  THE NTSB DID NOT CLASSIFY THIS AS AN ACCIDENT.

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.