ERA23FA235 · Honda Aircraft Co LLC HA-420 APMG
Honda Aircraft Co LLC HA-420 APMG · Accident: runway excursion during landing
From Wilkes County Airport (UKF) to an unrecorded destination
Event
- NTSB case
- ERA23FA235
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Honda Aircraft Co LLC HA-420 APMG
- Aircraft type
- Honda HA-420
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N255HJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wilkes County Airport (UKF), Wilkes County, NCTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was attempting to land on a wet, 5,000-ft-long asphalt runway in night conditions with calm wind. He stated that the airplane touched down before the 1,000 ft markers and that he immediately applied full brake pressure. The brakes began to cycle in anti-skid mode, but the pilot said the cycling felt slower than normal. The pilot considered a go-around, but the left brake “grabbed” suddenly, and the airplane yawed left and began a sequence of left and right skids before it continued off the end of the runway. The airplane traveled down an embankment onto a rocky berm and came to rest about 360 ft from the end of the runway. The pilot and the passengers egressed the airplane uninjured before a post-impact fire consumed the cockpit, center fuselage, and the right wing. The pilot stated that he used the airplane’s cockpit display unit (CDU) computer to calculate the airplane’s landing reference speed (Vref) of 120 knots (kts) and reported that the airplane touched down at this speed. Although recorded data for the flight was not available due to thermal damage to the avionics, ADS-B data last captured the airplane on final approach at a groundspeed of 120 kts, about 200 ft above the runway, consistent with the pilot’s statement. However, when the conditions that existed at the time of the accident were entered into an exemplar CDU, the calculated Vref was 112 kts, and the required landing distance for a wet/contaminated runway was 4,829 ft. To determine the landing distance required at a Vref of 120 kts, a Vref increment of Vref+5 (117 kts) and Vref+10 (122 kts) were entered into the CDU; the results were 5,311 ft and 5,794 ft, respectively. When these landing distances were calculated, the CDU, which had already been programmed for a 5,000-ft-long runway, displayed a prominent caution below the Vref number that stated: “LANDING FIELD LENGTH INSUFFICIENT.” How the accident pilot achieved a Vref of 120 kts via the CDU based on the conditions that existed at the time of the accident could not be determined. Postaccident examination of the braking system revealed no evidence of any preimpact anomalies or malfunctions that would have precluded normal operation; however, a testing anomaly was observed when the power brake and antiskid valve were tested. An initial test on an exemplar bench stand produced hysteresis that could not be produced when it was tested on a certified bench at the manufacturer. According to the manufacturer, the anomaly observed would not prevent the application of brakes nor the removal of pressure during skidding events; however, significant hysteresis may lead to braking performance degradation due to a decreased pressure application for a given current input. The reason for the anomaly was unknown, and therefore, it could not be determined if it played a role in the loss of braking action reported by the pilot. Despite this anomaly, and based on all other available information, the pilot landed the airplane faster than the prescribed landing speed with insufficient runway length available given the wet runway condition, which resulted in a runway excursion.
Probable cause
The pilot’s improper calculation of the airplane’s landing approach speed and required landing distance, which resulted in the airplane touching down fast with inadequate runway available, and a subsequent runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23FA235
- Event ID
- 20230518180442
- Case number
- ERA23FA235
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: ec341d19bef0007e3eb70d1c255574232d4f6359a2b31d4026d534843141d17d; retrieved 2026-09-16T17:37:03.491Z.