FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC06IA229 · American Blimp Corp. A-60+

26 Sept 2006 · Manchester, MA, United States

American Blimp Corp. A-60+ · Incident: airframe, component or system failure while standing

From Beverly Regional Airport (BVY) to Beverly Regional Airport (BVY)

Report a problem

Event

NTSB case
NYC06IA229
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
Incident
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
Unknown
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

American Blimp Corp. A-60+

Aircraft type
American Blimp A-60
Category
Blimp
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
N614LG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Beverly Regional Airport (BVY), Beverly, MATo Beverly Regional Airport (BVY)
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
Standing · engine(s) operating
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
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
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Flt control syst, rudder control › Malfunction
  • Pilot in command › Aircraft preflight, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Prior to departure, the operator's maintenance personnel performed engine starts, runups, and pressure checks. While a mechanic was performing the engine runups, a gust of wind kited the blimp and then forced it down, fully collapsing the wheel strut which was mounted to a truss assembly in the bottom of the control car in close proximity to the rudder control system's idler shaft assembly drive sprockets. The pilot of the blimp who witnessed the incident, discussed the incident with a mechanic, then entered the control car and moved the rudder pedals and control wheel each way to insure that there were no flight control restrictions; however, prior to departure, the pilot did not perform a pre-unmasting flight control check with the aid of the crew chief, which was required by the aircraft flight manual. After applying power and lifting off, the nose of the blimp began to move left. The pilot could not arrest the turn with the application of right rudder. There was no response or feedback from the rudder and the blimp began to drift to the east. The pilot tried to steer using differential power but, when he added power on either engine, it only increased the rate of turn to the left. As the blimp continued to drift eastward while simultaneously turning left, the blimp approached a metropolitan area and the Atlantic Ocean. The pilot then descended so that if the blimp drifted towards an "open" area, a rapid descent could be initiated to the ground. The descent was then continued by venting helium from the blimp's envelope. As the blimp continued to descend the pilot realized that there were no open areas in which to land, and as the blimp was headed into the wind, he brought both engines to idle and held both helium valves full open until the blimp settled into trees. Post incident examination of the blimps rudder control system revealed that the pedal cable/chain assembly had slipped off of the idler shaft assembly outboard drive sprocket. Further examination revealed that the sprocket was partially surrounded by two metallic tabs, one located above the sprocket, and one located below the sprocket, which acted as a chain keeper guard; however, the front and left side of the sprocket was unguarded.

Probable cause

A malfunction of the rudder control system, and the pilot's inadequate preflight inspection. Contributing to the incident was the inadequate design of the chain keeper guards.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC06IA229
Event ID
20061027X01568
Case number
NYC06IA229
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, coordinates. 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: c65b7a9c002b8f4bca051c4ba633a3cdde9ad10db6d397fcf467d0f9e64fd8b2; retrieved 2026-09-22T04:23:56.687Z.