# Incident 20230528017479I: Beech A36TC, Monterey, CA, May 28, 2023

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 28, 2023, 16:25 local time
- Place: Monterey, CA
- Airport: Monterey Regional Airport
- Damage: Minor damage
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 36.5870° N, 121.8428° W: Placed by OpenAirDocs at MONTEREY RGNL (MRY), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=36.5870&lon=-121.8428&mi=10
- Aircraft: N171PF, registered now (https://openairdocs.org/aircraft/N171PF) (OpenAirDocs)
- Registry model: Beech A36TC (registry code 1151603, https://openairdocs.org/model/beech-a36tc) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: BEECH A36TC
- Reported engine: CONT MOTOR TSIO-520 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 4,449 total, 4,449 in this make and model, 42 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20230528017479I

## Narrative

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

ON MAY 28, 2023, AT 15:41, THE FLIGHT DEPARTED FROM KLVK AIRPORT UNDER AN IFR FLIGHT PLAN. THE PILOT CONFIRMED THE TOWER PROVIDED A COMPLETE ROUTE CLEARANCE, AND THE AIRCRAFT TOOK OFF FROM KLVK, ADHERING TO IFR FLIGHT RULES.

THE PILOT ALSO CONFIRMED WHILE FLYING ON V111, AIR TRAFFIC CONTROL (ATC) NOTIFIED THE PILOT THAT THEY WERE CLEARED TO PROCEED DIRECTLY TO RUNWAY 28L APPROACH AS REQUESTED. THE PILOT STATED, ATC FURTHER INFORMED THE PILOT THAT A JET AIRCRAFT WAS FOLLOWING CLOSELY ON THE APPROACH AND REQUESTED EXPEDITED COMPLETION. THE PILOT PROMPTLY AGREED TO EXPEDITE.

THE PILOT STATED, HE FOLLOWED THE INSTRUMENT APPROACH CHECKLIST, AND RECEIVED CLEARANCE FOR THE APPROACH. WHILE PERFORMING THE LANDING CHECKLIST, THE PILOT NOTICED THAT THE AIRCRAFT'S SPEED WAS ABOVE THE RECOMMENDED RANGE FOR DEPLOYING THE LANDING GEAR AND FLAPS. A MENTAL NOTE WAS MADE TO LOWER THE LANDING GEAR AT A LATER STAGE.

FURTHERMORE THE PILOT STATED, HE WAS FOCUSED ON THE MESSAGES DISPLAYED ON HIS NEW AVIONICS. IT WAS DURING THIS TIME THAT THE PILOT REALIZED THE AIRCRAFT WAS DIRECTLY OVER THE RUNWAY.

FINALLY, ACCORDING TO THE PILOT AT THIS PHASE OF FLIGHT THE PILOT STATED, HE REDUCED POWER TO IDLE, AND UPON HEARING THE GEAR WARNING HORN THE PROPELLER TIPS MADE CONTACT WITH THE RUNWAY SURFACE. DUE TO PROPELLER STRIKES, THE PILOT MADE A GEAR-UP LANDING. MAINTAINING IDLE POWER, THE AIRCRAFT SLID ALONG THE RUNWAY UNTIL IT CAME TO A COMPLETE STOP, SLIGHTLY TO THE RIGHT OF THE CENTERLINE. THE PILOT STATES HE IMMEDIATELY INFORMED THE TOWER OF THE WHEELS-UP LANDING, SHUT DOWN ALL ELECTRICAL SYSTEMS, TURNED OFF THE MAGNETOS, AND EXITED THE AIRCRAFT WITHOUT SUSTAINING ANY INJURIES. NO FIRE OR FUEL SPILL OCCURRED AS A RESULT OF THE INCIDENT.

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.