NYC89FA221 · Aeronca 65TL
Aeronca 65TL · Accident: airframe, component or system failure on approach
From Beaver County Airport (BVI) to an unrecorded destination
Event
- NTSB case
- NYC89FA221
- 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
- 1 · 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 65TL
- Aircraft type
- Aeronca 65
- 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
- N33890
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Beaver County Airport (BVI), Beaver Falls, PATo 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
- Approach · VFR pattern downwind
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Maintenance, inspection, inadequate
- Wing, bracing strut › Separation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT-IN-COMMAND SPENT SEVERAL YEARS REBUILDING THE AIRPLANE AT HIS OWN LEISURE. THE LOGBOOKS INDICATED THE LAST ANNUAL WAS COMPLETED IN 1986. IT WAS NOT KNOWN IF THE AIRPLANE HAD FLOWN SINCE THAT ANNUAL PRIOR TO THIS FLIGHT. FRIENDS STATED THE PILOT-IN-COMMAND WAS ONLY GOING TO TAXI THE AIRPLANE AND PERFORM SOME RUN-UP TESTS. HOWEVER, THE PILOT-IN-COMMAND ELECTED TO FLY THE AIRPLANE. WHILE ON DOWNWIND, THE LEFT WING APPEARED TO FOLD UP, THE AIRPLANE ROLLED LEFT, NOSED OVER AND DESCENDED RAPIDLY BEHIND TREES. EXAMINATION OF THE WRECKAGE REVEALED THAT THE RETAINING BOLT AND NUT FOR THE LEFT WING REAR UPPER STRUT ATTACHMENT WAS NOT INSTALLED.
Probable cause
THE FAILURE OF THE LEFT WING, REAR UPPER STRUT ATTACHMENT. THE FAILURE WAS CAUSED BY NOT INSTALLING THE RETAINING BOLT AND NUT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC89FA221
- Event ID
- 20001213X29474
- Case number
- NYC89FA221
- 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: 7684b953ece0d6305f4260d1ebb28876bd07e00eb4a1a05a18ee05e7576f2887; retrieved 2026-09-21T03:08:01.601Z.