WPR13CA162 · Boeing B75N1
Arizona Wing Commemorative Air Force Boeing B75N1 · Accident: loss of control on ground during landing
From Falcon Field (FFZ) to Falcon Field (FFZ)
Event
- NTSB case
- WPR13CA162
- 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
Boeing B75N1
- Aircraft type
- Boeing B75
- 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
- N47964
- Onboard fatalities
- Unknown
- Route
- From Falcon Field (FFZ), Mesa, AZTo Falcon Field (FFZ), Mesa, AZ
- 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
- Loss of control on ground
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that as the tailwheel-equipped airplane decelerated after touchdown, it tracked left of the runway centerline. He applied corrective control inputs; however, the airplane continued to track left and departed the runway. The right wing contacted the ground and was substantially damaged during the runway excursion. The pilot reported that during the recently completed 100-hour annual inspection, the tailwheel suspension strut was modified with a different type of strut and that the new strut did not compress on landing until after right rudder was applied. However, review of the tailwheel strut design revealed that the strut only affects the vertical movement of the tailwheel, and has no lateral control effects. Postaccident examination of the airplane revealed no evidence of a mechanical failure or malfunction that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control during the landing roll.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13CA162
- Event ID
- 20130326X25453
- Case number
- WPR13CA162
- 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. 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: 327ed2ca7aa0e201b80f9aca8a989fa5bfa01fbb9027b5b556f412b21dbf5d08; retrieved 2026-09-15T21:09:47.947Z.