FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC82FNA19 · Breezy RL4-1

9 Jul 1982 · Andover, MA, United States

Breezy RL4-1 · Accident: airframe, component or system failure en route

From Tewksbury, MA to North Hampton, NH

Report a problem

Event

NTSB case
NYC82FNA19
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

Breezy RL4-1

Aircraft type
Breezy RL4
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
N2343
Operator
Frank Vogt
Onboard fatalities
Unknown
Route
From Tewksbury, MATo North Hampton, NH
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
En route · cruise
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
Substantial

Cause areas

  • Fuselage, longeron › Cracked
  • Fuselage, longeron › Failure, partial

Approximate · Estimated position: the centre of Andover, MA, the place the record names. Not the accident site.

NTSB narrative

DURING FLT THE PLT FELT SOMETHING SNAP OR BREAK ON THE ACFT. THE CONTROL WHEEL MOVEMENT FOR THE AILERON BECAME EXCEEDINGLY HARDER TO MOVE & THE ACFT STARTED TO FLUTTER IN AN UP & DOWN MOTION. HE REDUCED POWER TO SLOW THE FLUTTERINGACTION, BUT WAS NOT ABLE TO MAINTAIN ALTITUDE, AN EMERGENCY LANDING WAS MADE ON A GOLF COURSE & THE ACFT ROLLED INTO A SAND TRAP. INVESTIGATION REVEALED THAT THE UPPER LEFT LONGERON LOCATED NEAR THE REAR PLT'S SEAT WAS BROKEN & THE TUBING SPLIT. IT HAD FAILED JUST BEHIND THE REAR SEAT AT THE TUBING CLUSTER WELD. THE CRACK STARTED AT THE REAR EDGE OF THE CLUSTER WELD IN THE AREA WHICH SHOWED THE MOST HEAT PENETRATION OF THE BASE METAL THEN PROGRESSING AROUND THE TUBE.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC82FNA19
Event ID
20020917X04058
Case number
NYC82FNA19
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: 27d3663c8cffae60ec8c9591a8ebbda32eaf89e3fb9d52d592051219859bb858; retrieved 2026-09-24T02:30:24.666Z.