WPR25LA271 · Naval Aircraft Factory N3N-3
Naval Aircraft Factory N3N-3 · Accident: collision during takeoff/landing
From Priv · Columbus, MT to an unrecorded destination
Event
- NTSB case
- WPR25LA271
- 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
Naval Aircraft Factory N3N-3
- Aircraft type
- Naval Aircraft Factory N3
- 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
- N45254
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Priv · Columbus, MTTo not recorded
- Aircraft age
- About 84 years (built 1941)
- 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 · aborted after touchdown
- 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
- Collision during takeoff/landing
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, while landing he executed a go around due to numerous people on the grass runway. On the second approach the airplane touched down hard and bounced so the pilot added power and initiated a go-around. During the go-around, the airplane impacted a wire fence at the end of the runway and subsequently struck powerlines before it came to rest. The airplane sustained substantial damage to the wings and fuselage. The pilot reported that he had previously only flown low approaches at the airport, and he had not landed there before. He also reported there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. The nearest weather reporting station, about 27 miles southeast of the accident site, reported around the time of the accident, altimeter setting of 30.31 inches of mercury, and temperature of 68° F. The calculated density altitude was 7,349 ft.
Probable cause
The pilot’s failure to maintain clearance from obstacles during an aborted landing. Contributing to the accident was the high density altitude weather condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR25LA271
- Event ID
- 20250902200922
- Case number
- WPR25LA271
- 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: 8dbdd3987ede83833df5ed5dac48180d6c97d791bb9f1003cf2a7b755ea6d6d3; retrieved 2026-09-16T20:17:53.115Z.