# Incident 20230404003039I: Cessna T210M, Manassas, VA, April 4, 2023

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 4, 2023, 18:50 local time
- Place: Manassas, VA
- Airport: Manassas Regional
- Damage: Minor damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.7468° N, 77.4826° W: Placed by OpenAirDocs: center of Manassas, VA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.7468&lon=-77.4826&mi=10
- Aircraft: N761TY, registered now (https://openairdocs.org/aircraft/N761TY) (OpenAirDocs)
- Registry model: Cessna T210M (registry code 2073451, https://openairdocs.org/model/cessna-t210m) (OpenAirDocs)
- Registry engine: Continental TSIO-520 series (registry code 17040, https://openairdocs.org/engine/continental-tsio-520-series) (OpenAirDocs)
- Reported make and model: CESSNA T210M
- Reported engine: CONT MOTOR TSIO-520 SER
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 1,114 total, 572 in this make and model, 14 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20230404003039I

## Narrative

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

PIC STATED THAT ON FINAL APPROACH, THE GEAR INDICATOR WAS GREEN AND THAT THE GEAR WAS DOWN ACCORDING TO THE WING MIRRORS. ON LANDING FLARE HE HEARD A SCRAPING NOISE, ADDED FULL POWER AND INITIATED A CLIMB TO ENTER THE TRAFFIC PATTERN AGAIN. ON TROUBLESHOOTING HE NOTICED THE GEAR PUMP CIRCUIT BREAKER WAS POPPED. UPON PUSHING IT IN THE GEAR CAME DOWN AND LOCKED, FOLLOWED BY A NORMAL LANDING. I USED COUNSELING TO REVIEW EVENTS LEADING TO THE INCIDENT, HIGHTLIGHTING THE HAZARD OF EXPECTATION BIAS, WHEN WE SEE WHAT WE WANT TO SEE RATHER THAN REALITY. THIS WAS IDENTIFIED AS THE ROOT CAUSE OF THE INCIDENT. THE GEAR WAS CLEARLY FULLY RETRACTED ON THE FIRST APPROACH. I USED COUNSELING TO IMPLEMENT PROCEDURAL CHANGES TO MITIGATE

THIS TENDENCY IN THE FUTURE. WE ALSO DISCUSSED RISK MANAGEMENT PRINCIPLES APPLICABLE TO THE DECISION TO GO AROUND AFTER THE PROP STRIKE, AS OPPOSED TO LANDING STRIGHT AHEAD ON THE BELLY.

## Other reports on N761TY (1)

Matched to the same aircraft by N-number and date.

- [Incident 20110812018099I](https://openairdocs.org/incident/20110812018099I), Aug 12, 2011: Cessna T210M (N761TY), Westminster, MD, Minor damage. On August 12, 2011, aircraft N761TY departed from brandywine headed to manassas. The pilot was [privacy data omitted]. While enroute, the pilot experienced a…

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.