NYC95LA118 · Aeronca O-58B
Aeronca O-58B · Accident: in flight collision with object during initial climb
From Air Haven Airport (6PA6) to an unrecorded destination
Event
- NTSB case
- NYC95LA118
- 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
Aeronca O-58B
- Aircraft type
- Aeronca O-58
- 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
- N46181
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Air Haven Airport (6PA6)To not recorded
- 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
- Initial climb
- First occurrenceThe 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Pole
- 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
- Pilot in command › Clearance, not maintained
- Pilot in command › Compensation for wind conditions, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS DEPARTING TO THE NORTH FROM A GRASS RUNWAY AND DURING THE INITIAL TAKEOFF CLIMB AFTER TAKEOFF, THE AIRPLANE DRIFTED RIGHT OF THE RUNWAY CENTERLINE. THE RIGHT WING STRUCK A WIND SOCK POLE AND THE AIRPLANE YAWED TO THE RIGHT AND TOWARDS TREES. WITNESSES SAW THE AIRPLANE ROLL TO THE RIGHT, UNTIL IT BECAME INVERTED AND STRUCK THE GROUND. EXAMINATION OF THE WRECKAGE REVEALED NO PRE-IMPACT FAILURE OF THE AIRPLANE OR ENGINE. THE PILOT STATED THAT DURING THE TAKEOFF ROLL, HE APPLIED AILERON AND RUDDER TO CORRECT FOR A CROSS WIND; HOWEVER, THE RIGHT WING STRUCK 'TREES.' THE PILOT ESTIMATED THE WINDS WERE FROM 270 DEGREES AT 6 TO 8 KNOTS. WINDS REPORTED AT AN AIRPORT 10 MILES WEST, WERE FROM 290 DEGREES AT 7 KNOTS.
Probable cause
The pilot's inadequate compensation for a cross wind and his failure to maintain adequate obstacle clearance. A factor is the crosswind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95LA118
- Event ID
- 20001207X03541
- Case number
- NYC95LA118
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 75ea596e4175ccdbfad7bbfcc15960b24699199788c93649713ea0078cb024fe; retrieved 2026-09-21T13:17:05.428Z.