ANC24LA028 · Team Rocket F1 EVO
Team Rocket F1 EVO · Accident: abnormal runway contact during landing
From Glendale Municipal Airport (KGEU) to an unrecorded destination
Event
- NTSB case
- ANC24LA028
- 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
Team Rocket F1 EVO
- 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
- N75KM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Glendale Municipal Airport (KGEU), Glendale, AZTo not recorded
- Aircraft age
- About 15 years (built 2009)
- 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
- 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
- Abnormal runway contact
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, while landing with a left crosswind, the airplane bounced slightly on initial touchdown, and it drifted to the right of the centerline. The pilot applied left aileron and left rudder to correct for the veer and added engine power to abort the landing, but a gust of wind rolled the airplane to the right, and the right wing struck the runway. Subsequently, the pilot elected to land the airplane on the remaining portion of the runway. During the second touchdown on the right side of the runway, the pilot said he lost directional control. The airplane travelled laterally across the runway surface and exited the left side of the runway, bending the right landing gear leg backward and the airplane nosed down. The airplane sustained substantial damage to the wings and engine mount tube structure. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control while landing in gusting crosswind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC24LA028
- Event ID
- 20240423194138
- Case number
- ANC24LA028
- 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, 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: 66e7e67be35a0c2af08f2ecec157ad5d800c31c82b4a87b242f9949a7d88d267; retrieved 2026-09-16T18:41:40.868Z.