NYC83FU004 · Vector 610
Vector 610 · Accident: airframe, component or system failure while maneuvering
Event
- NTSB case
- NYC83FU004
- 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
Vector 610
- Aircraft type
- Vector 610
- Category
- Ultralight
- 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
- UNREG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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 103: Ultralight
- 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
- Maneuvering
- 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
- Pilot in command › Maintenance, major repair, improper
- Wing › Failure, total
- Wing, wingtip › Loose
Approximate · Estimated position: the centre of Turners Falls, MA, the place the record names. Not the accident site.
NTSB narrative
ON 4/18/83, THE ULTRALIGHT VEHICLE WAS DAMAGED BY HIGH WINDS. THIS NECESSITATED THE REPLACEMENT OF THE FRONT & REAR SPARS AS WELL AS THE BATTENS WHICH PROVIDED CURVATURE TO THE UPPER WING SURFACE. PRIOR TO A TEST FLT, A WEIGHTED TAIL WHEEL WAS ALSO INSTALLED. SUBSEQUENTLY, A TEST PLT TOOK OFF TO EVALUATE THE ULTRALIGHT. WITNESSES OBSERVED THAT THE PLT CLIMBED TO ABOUT 1000 FT, THEN BEGAN A SERIES OF MANEUVERS. WHILE PERFORMING A MANEUVER, SIMILAR TO A LAZY 8, WITH BANK ANGLES UP TO 60 TO 90 DEG, THE ULTRALIGHT'S LEFT WING FOLDED. THE VEHICLE THEN ENTERED AN UNCONTROLLEDDESCENT & CRASHED. AN EXAM OF THE WRECKAGE REVEALED THAT THE AFT SPAR TIP HAD ROTATED AROUND THE AFT SPAR IN SUCH A MANNER THAT THE OUTBOARD WING PANEL HAD BENT DOWN & REARWARD. HOLES HAD NOT BEEN DRILLED & STEEL POP RIVETS HAD NOT BEEN INSTALLED, PER INSTALLATION INSTRUCTIONS, TO PREVENT THE SPAR TIP FROM ROTATING. ALSO, THE PLT'S BLOOD ALCOHOL LEVEL WAS FOUND TO BE 95 MG%. THE TEST PLT ALSO PERFORMED MAINTENANCE ON THE ULTRALIGHT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83FU004
- Event ID
- 20001214X43121
- Case number
- NYC83FU004
- 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: 0fe0d902ac429f852d271a9cc752bddcef2252d8a87ccbcdf74d1003d934c3ff; retrieved 2026-09-21T06:49:38.765Z.