20240107001612A

Accident · Substantial damage

FAA accident report · Cessna 421C · Carson City, NV · January 7, 2024

Date
January 7, 2024 · 18:10 local
Place
Carson City, NV
Airport
Carson City Airport
Phase of flight
Landing: Rollout
Operating rules
General operating rules (Part 91)
Collision
Collision on the ground
Damage
Substantial damage
Aircraft
N421TP
NTSB investigation
NTSBWPR24LA068
Reported as
Cessna 421C
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificates
Airline transport, flight instructor
Pilot’s flight hours
3,638 total

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.

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.

As the FAA filed it

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.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other aircraft in the event · 1

Each aircraft in a collision has its own report.