12 Jan 2024: HARMON ROCKET II

12 Jan 2024: HARMON ROCKET II (N630L) — Unknown operator

No fatalities • Mesquite, NV, United States

Probable cause

The pilot’s loss of control on the landing roll, which led to the airplane coming to rest inverted.

— NTSB Determination

Accident narrative

On January 12, 2024, about 1515 Pacific Daylight time, an experimental amateur-built Harmon Rocket II airplane, N630L, was substantially damaged when it was involved in an accident near Mesquite, Nevada. The pilot was seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.   The pilot’s mechanic stated that the day before the accident, he performed maintenance on the right main landing gear brake system. He stated that after completing the maintenance, he advised the pilot to use caution during the first few brake applications to allow the system to wear in and recommended that the pilot perform at least three fullstop landings. On the day of the accident, the mechanic reported that he and the pilot ate lunch together, after which he observed the pilot perform several taxi brake checks before departing.   A witness reported observing the tailwheelequipped airplane during the landing roll on runway 20. The airplane was right of the runway centerline and continued to veer right as ground speed decreased. The airplane then pitched forward, and the propeller contacted the runway surface. The airplane continued to slide forward, departed the right side of the runway, and nosed over, coming to rest inverted and oriented about 90° to the right of the runway heading.

Witnesses who responded immediately after the accident reported that the canopy was broken into pieces on the pavement. The pilot remained restrained by the seatbelt, with his head pressed against the canopy. One witness assessed the pilot and was unable to detect a radial or carotid pulse. Based on this assessment, responders extricated the pilot and initiated cardiopulmonary resuscitation (CPR). After approximately 4 minutes of CPR, a pulse returned, and the pilot was placed on a cardiac monitor, which indicated intermittent bradycardia. The pilot was resuscitated and transported to a hospital with serious injuries, including neurological injury that rendered him unable to communicate any history of the event. No significant preimpact medical condition was identified during his hospitalization. A hospital urine drug screen performed two days after admission did not detect any testedfor substances not attributable to postaccident medical treatment. The pilot died over 30 days after the accident.

According to the pilot’s FAA medical certification file, his most recent aviation medical examination was conducted on December 7, 2023, at which time he was issued a firstclass medical certificate with no limitations.

According to a witness, the first identified point of contact with the runway occurred about 1,200 ft from the approach end of runway 20, where tire marks were observed near the runway centerline. The tire marks subsequently veered right, and multiple propeller strike marks extended approximately 30 ft down the runway. Pieces of the wooden propeller were located in this area. Tire marks continued to the right of the runway, and propeller strike marks resumed approximately 150 ft beyond the initial strike marks. The witness reported that runway markings indicated the airplane pitched forward and slid on the propeller hub and fuselage until it reached the right edge of the runway and entered the adjacent deep gravel. Depressions in the gravel were consistent with the airplane flipping over and coming to rest inverted along its longitudinal axis (see figures 1 and 2). The pilot’s mechanic stated that from the tire marks, it appeared the pilot was applying brakes at the same time the engine was producing power.

Figures 1 and 2: The tire marks showing the propeller strike marks and the main wreckage showing orientation to the runway.

Contributing factors

  • Directional control — Not attained/maintained
  • Pilot

Conditions

Weather
VMC, wind 240/03kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.