ERA25LA192 · Boeing A75N1(PT17)
Ageless Aviation Dreams Foundation Boeing A75N1(PT17) · Accident: abnormal runway contact during landing
Event
- NTSB case
- ERA25LA192
- 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
- 0
- 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
Boeing A75N1(PT17)
- Aircraft type
- Boeing A75
- 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
- N65011
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 83 years (built 1942)
- 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
- 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 of the vintage, tailwheel-equipped airplane reported that the wind was gusty and variable in direction for the flight in the airport traffic pattern. The pilot reported asking air traffic control to land on runway 13 and was told by the controller that winds were “all over the place.” The pilot then elected to continue to land on runway 5, the runway currently in use. After performing a normal 3-point landing, the airplane began to weathervane to the right and the right wing raised up, resulting in the left wing impacting the runway, substantially damaging it. The pilot reported there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation. A weather observation taken about 7 minutes prior to the accident reported the wind was from 100° at 16 knots, gusting to 23 knots. The crosswind component for runway 5 was calculated to be about 12 knots from the right, with the gust crosswind component reaching about 18 knots from the right. The crosswind component for runway 13 was calculated to be about 8 knots from the left, with the gust crosswind component reaching about 11 knots from the left.
Probable cause
The pilot’s failure to maintain directional control of the airplane while landing in gusting crosswind conditions, which resulted in the left wing impacting the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA192
- Event ID
- 20250501200087
- Case number
- ERA25LA192
- 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: e9872ec971017de9e0252fb640da2c83c4d81248729de45a56b7c4a1a8d14c12; retrieved 2026-09-16T19:51:32.292Z.