# Accident 20240107001612A: Cessna 421C, Carson City, NV, January 7, 2024

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 7, 2024, 18:10 local time
- Place: Carson City, NV
- Airport: Carson City Airport
- Damage: Substantial damage
- Collision: Collision on the ground
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 39.1922° N, 119.7332° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.1922&lon=-119.7332&mi=10
- Aircraft: N421TP, registered now (https://openairdocs.org/aircraft/N421TP) (OpenAirDocs)
- Registry model: Cessna 421C (registry code 2076016, https://openairdocs.org/model/cessna-421c) (OpenAirDocs)
- Registry engine: Lycoming LTP101-600A (registry code 41566, https://openairdocs.org/engine/lycoming-ltp101-600a) (OpenAirDocs)
- Reported make and model: CESSNA 421C
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, flight instructor
- Pilot flight hours: 3,638 total
- NTSB investigation: [NTSB WPR24LA068](https://openairdocs.org/ntsb/WPR24LA068) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20240107001612A

## Narrative

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

IFR FLIGHT PLAN ROUTE

UPON LANDING ROLLOUT (ABOUT 25-35 KNOTS) PILOT FELT AND HEARD A THUD AND AT THAT MOMENT SAW A DISABLED AIRCRAFT OUT OF HIS PERIPHERAL VISION.  PILOT NOTICED THAT HE HAD JUST STRUCK A DISABLED AIRCRAFT OF THE LEFT SHOULDER OF RUNWAY 27 WITH HIS LEFT WINGLET.  PILOT DID NOT APPROPRIATELY NOTIFY CORRECT AGENCIES OF ACCIDENT UNTIL THE FOLLOWING DAY WHEN FAA ARRIVED TO INVESTIGATE DISABLED AIRCRAFT OCCURRENCE.

PILOT STATED THERE WAS NO NOTAM, AWOS REPORT, INDICATION ON RUNWAY OR OTHER MARKINGS TO IDENTIFY A CLOSED RUNWAY OR WHERE THE DISABLED AIRCRAFT WAS LOCATED.  PILOT STATES AFTER CANCELING IFR TO KMEV, ATC DID NOT NOTIFY OF RUNWAY CLOSURE AT KCXP NOR WAS IT ON RECORDING CAPABLE AWOS AT KCXP WHILE PROCEEDING VFR TO KCXP.

PILOT NOTED NO NOTAMS ISSUED BEFORE TAKEOFF FROM VAN NYES OR ENROUTE BEFORE LANDING AT KCXP.

AIRPORT MANAGER STATED AN AIRPORT VOLUNTEER WAS TASKED TO MONITOR CTAF AND N421TP GAVE A POSITION CALL, BUT NEVER RESPONDED TO VOLUNTEERS ATTEMPTS TO INFORM N421TP THAT RUNWAY WAS CLOSED AT KCXP.

## Other aircraft in the event

- N819RL, Piper PA-46-600TP: [Incident 20240107000219I](https://openairdocs.org/incident/20240107000219I)

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB WPR24LA068](https://openairdocs.org/ntsb/WPR24LA068), Jan 8, 2024: Cessna 421C (N421TP), Carson City, NV, substantial damage. Probable cause: Airport personnel’s failure to properly prioritize their response actions, including updating the airport’s automated weather observation system recording in a timely manner to notify incoming pilots…

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.