ERA20CA291 · Team Rocket F1 Rocket
Team Rocket F1 Rocket · Accident: landing area overshoot
Event
- NTSB case
- ERA20CA291
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
Team Rocket F1 Rocket
- Aircraft type
- Team Rocket F1
- 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
- N88XK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 2 years (built 2018)
- 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
- Landing area overshoot
- 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
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
- Personnel issues › Physical
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The owner of the airplane had recently purchased it, and a pilot had ferried the tailwheel-equipped, tandem seat airplane across the country and delivered it to him the day before the accident. The purpose of the accident flight was for the ferry pilot to familiarize the owner with the airplane’s avionics. For the accident flight, the owner was seated in the front seat, while the ferry pilot (who did not hold a flight instructor certificate) was seated the rear. The airplane’s rear seat was equipped with a limited set of flight controls that included a control stick, rudder pedals, and throttle. The rear seat was not equipped to control the airplane’s brakes. The pilots departed and flew to a nearby airport with a 4,000-ft-long runway, where the owner flew an approach to landing that terminated in a go-around. The ferry pilot then demonstrated a touch-and-go landing. On the third approach attempt the owner was unable to extend the airplane’s flaps, so they aborted the approach to troubleshoot the problem. The pilots were ultimately unable to extend the flaps and elected to return to the owner’s home airport and land on the 2,500-ft-long runway there. When the ferry pilot initially attempted to land the airplane, it bounced during both attempts and he aborted the landings. The owner described that during the final landing attempt, the ferry pilot approached the runway at a “slightly faster speed” and that the airplane “landed long.” The airplane continued down the runway with its tail in the air. The ferry pilot, being unable to see the runway due to his vision being obstructed by his position in the rear seat, did not realize that the airplane was approaching the end of the runway until the owner called out to him. The owner stated that he began applying the airplane’s brakes with about 400 feet of the runway remaining. The airplane subsequently overran the departure end of the runway. During the excursion both main landing gear collapsed, and the forward portion of the fuselage and engine mount area were substantially damaged.
Following the accident, a Federal Aviation Administration (FAA) inspector responded to the accident site and during his examination of the wreckage he turned on the master switch and extended the airplane’s flaps. The flaps extended normally.
Probable cause
The pilot's misjudgment of the airplane’s speed and altitude during the landing approach, and his failure to attain the proper touchdown point during landing, which resulted in a runway overrun. Contributing to the accident were his access to a limited set of flight controls, his obstructed vision due to his seating position, and the pilot’s decision to return to the relatively constrained runway following a perceived anomaly of the airplane’s flaps.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA291
- Event ID
- 20200819X75908
- Case number
- ERA20CA291
- 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: e96a0469f241a347a4a8ce165084163cd4ea3a6b44d2e0bdc448d4c77a56755c; retrieved 2026-09-16T12:50:39.210Z.