The U.S. aircraft register, updated daily
Accidents · NTSB WPR24LA068 · Final report

Cessna 421C accident near Carson City, Nevada, January 8, 2024

On January 8, 2024 at about 4:19 am local time, a 1977 Cessna 421C, registered N421TP, was substantially damaged in an accident during prior to flight near Carson City, Nevada (Carson City airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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 of a runway closure, which resulted in an airplane striking an immobilized airplane on the runway during landing at night. Contributing to the accident was the airport’s inadequate emergency response plan.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 8, 2024 · about 4:19 am local time
Place
Carson City, Nevada · Carson City · map
Type
Accident · collision on the ground
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 421C, built 1977 · all 421Cs on the register
Registration
N421TP · registry record · serial 421C0258
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot was conducting a return flight at night to his original departure airport on an instrument flight rules (IFR) flight plan. Before departing he checked the weather at his destination and the Notices to Airmen (NOTAMs) and there were no restrictions to returning to the non-towered airport. After the pilot departed for his destination, a second pilot landed at the destination airport after business hours. That pilot lost control during landing and that airplane slid off the side of runway 27 and came to rest with the left wing partially blocking the runway. That pilot contacted flight service (FS), who notified the airport manager of the blocked runway and issued a notice to airmen (NOTAM) that the runway was closed. Airport personnel were contacted to respond to the disabled airplane and a resident near the airport was contacted to monitor the airport’s common traffic advisory frequency (CTAF) and notify any inbound aircraft that the runway was closed. The first airport employee to arrive at the airport proceeded to the disabled airplane so he could transport the pilot and his dog to the airport terminal. After they returned to the terminal, a second airport employee arrived. The first employee and the pilot then returned to the disabled airplane to take photographs. The second employee remained at the terminal to watch the pilot’s dog. Airport personnel did not immediately update the Automated Weather Observation System (AWOS) recording to warn incoming aircraft of the runway closure or put closed runway lighting in place on the runway. While enroute, the pilot checked the weather and AWOS and there were no warnings of the runway closure at his destination. Due to the reported weather and because there was not an instrument approach approved for night use at his destination, he instead changed his plan and route of flight to fly an instrument approach to a nearby airport to use it as a waypoint, then cancel IFR once he was below the weather and continue the flight to his original destination under visual flight rules(VFR). The pilot did not inform air traffic control (ATC) of his plans, nor was he required to, so they did not provide available NOTAM information that the runway was closed at his destination. The pilot flew the IFR approach, canceled his IFR clearance and proceeded to the destination airport under VFR as planned. The pilot rechecked the AWOS as he neared the destination airport and made a 10-mile position call on the CTAF. The airport resident monitoring the airport’s CTAF frequency heard someone attempt to activate the runway lights and heard the pilot’s 10-mile position call. The resident attempted to contact the pilot on the radio multiple times, but did not receive a reply. Airport personnel, who had handheld and vehicle mounted radios, did not hear either the pilot’s or the resident’s radio transmissions. The pilot did not hear any radio transmissions on the Unicom frequency warning of the runway closure and subsequently landed. He was unaware of the airplane blocking the runway until he hit it. The left winglet on the landing airplane had impacted the airplane blocking the runway, substantially damaging the landing airplane’s left aileron. The airport’s emergency response plan did not provide for specific actions to be taken by personnel in the event of a non-accident runway closure event. The emergency response plan was updated following this accident with specific actions for personnel to take in the event of an aircraft accident or incident, including the issuance of a NOTAM and updating AWOS to advise of any closure or hazard at the airport. The airport manager stated it would take about 5 minutes for someone inside the terminal to update the AWOS. The pilot made reasonable attempts to determine the status of the airport before landing. There was insufficient evidence to determine why the pilot did not hear the resident attempting to warn him of the runway closure. The accident is consistent with airport personnel not properly prioritizing their actions in response to the disabled airplane in order to prevent another airplane from landing on the closed runway.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Airport occurrence during prior to flight defining event
  2. Runway incursion veh/AC/person during landing (landing roll)

The NTSB's findings

  • Organizational issues › Management › (general) › (general) › Other institution/organization
  • Personnel issues › Action/decision › Action › Delayed action › Airport personnel
  • Personnel issues › Physical › Sensory ability/limitation › Visual function › Pilot
  • Environmental issues › Operating environment › Meteorological services › Automated weather › Accuracy of related info
  • Environmental issues › Operating environment › (general) › (general) › Ability to respond/compensate
  • Environmental issues › Physical environment › Object/animal/substance › Aircraft › Effect on operation
  • Environmental issues › Physical environment › Object/animal/substance › Aircraft › Ability to respond/compensate

Pilot

  • Certificate: airline transport pilot, flight instructor
  • Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane
  • Flight time: 9,993 hours in all; 258 in this make and model; 81 in the last 90 days; 28 in the last 30 days; 9,808 as pilot in command; 3,634 on instruments
  • Last flight review: March 4, 2023
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,638 hours
  • Last inspection: annual inspection, May 10, 2023
  • Maximum gross weight: 7,560 lb
  • Seats: 8
  • Landing gear: retractable
  • Engine 1: Lycoming LTP101-600A (turboprop); 3,002 hours total
  • Engine 2: Lycoming LTE101-600A (turboprop); 2,993 hours total
  • Operator: Double R Aviation LLC

The flight

  • Departed from: VNY Van Nuys CA at 2:20 am
  • Flight plan: IFR
  • Runway 09/2, 6,101 ft by 75 ft

Weather at the time

  • Light: night
  • Visibility: 10 statute miles
  • Sky: broken clouds at 4,300 ft
  • Temperature: 18°F (-8°C), dew point 12°F (-11°C)
  • Altimeter: 30.11 inHg
  • Observation at 8:10 pm from KCXP, 1 miles away

Weather report (METAR): KCXP 080410Z AUTO 00000KT 10SM BKN043 OVC055 M08/M11 A3011 RMK AO2

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

7 documents, released by the NTSB on October 22, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.