NTSB CAROL · Event
Event LAX95LA121
Aircraft involved
Probable cause & findings
the pilot's decision to operate the blimp with a known and unresolved deficiency in the electrical system, which led to a loss of the flight controls and the pilot's improper remedial actions after the blimp came to rest on the ground.
Factual narrative
On February 26, 1995, at 1522 Pacific standard time, the pilot of a Thunder & Colt GA42 blimp, N28SQ, fell from the aircraft during an attempted landing at the Hayward, California, airport. The airship was owned and operated by Sky Quest, Inc., of San Jose, California, and was conducting local traffic pattern operations at the airport. Visual meteorological conditions prevailed at the time and included calm wind conditions. The airship was not damaged in the accident sequence; however, the certificated commercial pilot incurred fatal injuries. The flight originated at the Hayward airport on the day of the accident at 1514 hours. Information provided by the blimp's ground crew revealed that the pilot was giving familiarization rides to ground crew members during the flight sequence. According to statements from the Federal Aviation Administration (FAA) Air Traffic Control Tower (ATCT) personnel on duty in the tower cab, the airship was performing closed traffic pattern stop-and-go operations in an area adjacent to runway 28L. The accident occurred during the third stop-and-go landing of the flight. While on downwind, the blimp was cleared for a stop-and-go option by the local controller. The passenger onboard the airship was interviewed by FAA inspectors. According to his written and oral statements, the pilot had given a paying passenger a sightseeing ride earlier in the day and the second individual scheduled for the day did not show up. The pilot then decided to give his ground crew familiarization rides. A circuit of the pattern was flown with another ground crew member. The witness then got in the gondola, and, in the process, accidently moved the mixture control and killed the engine. The pilot restarted the engine then motioned for the chief ground crew member and told him that he had a low-battery warning light, but thought he had enough remaining battery capacity to make one more circuit of the pattern. The witness said that during the traffic pattern flight, the low-battery light remained illuminated. During the approach, the pilot had to go-around due to an unfavorable wind gust. On downwind for the second landing attempt, the voltage dropped to about 4 and the pilot became very concerned. The pilot shut off all unnecessary electrical systems and turned directly toward the landing area. At that point, the electrical servo motors which move the control surfaces stopped working due to the low voltage. The blimp hit the grass short of the landing zone and bounced along the ground until it eventually stopped near the top of a noise abatement berm. The witness said the pilot told him to get out and hold the blimp by the ground handling rail. The witness said he tripped as he got out and rolled down the hill. By the time he got back on his feet, the blimp was rising past 20 feet agl with the pilot holding on to the railing. The pilot fell at about 200 feet. Statements were obtained from ground witnesses, including ATCT controllers in the tower cab and the pilot of an aircraft holding short of runway 28L for departure. The blimp appeared to turn directly toward the runway on a perpendicular path near the approach end on a short base leg, overshoot the runway, then turn back toward its normal landing area. During this time, there were no confirmed radio transmissions from the blimp; however, the airship ground crew members responded to the ATCT inquiry that the blimp was in trouble and that the pilot had lost control. The blimp touched down and bounced along the ground several times before it began drifting backwards across runway 28L at the displaced threshold. The blimp continued to bounce along the ground a few times before appearing to settle near a noise abatement berm with the engine running. The blimp came to rest about 100 yards from the ground crew. The passenger and pilot were observed to exit the gondola, then the blimp began to rise with the pilot hanging onto a ground handling rail near the bottom of the gondola. The witnesses stated that the pilot apparently lost his grip as the blimp rose and subsequently fell to the runway pavement from a height estimated at 200 feet. The blimp continued to rise and disappeared into the overcast. With the help of a fixed-wing aircraft, the unmanned airship was tracked as it ascended to an altitude of about 10,000 feet and drifted slowly northeast over the eastern San Francisco Bay area. After several hours, the blimp gradually descended. Trailing police and California Highway Patrol (CHP) helicopters hovered over the blimp and forced it to the ground in Orinda, California, where it became entangled in trees. Responding CHP and Orinda Police Department ground units reported that when they arrived at the airship, the engine was still running and was turned off by one of the officers. The battery master and alternator switch were found in the off position. FAA inspectors from the Oakland, California, Flight Standards District Office examined the airship with the assistance of a factory-trained airframe and powerplant mechanic. The blimp control system is powered by electrical servo motors. The examining inspector reported that the battery was weak and produced only 7 volts. All electrical system mode switches in the cockpit were found in the normal position and not in the emergency mode. The systems were powered up using the battery as found. All control system servo motors functioned normally. The alternator and voltage regulator would not charge the battery when tested in the gondola. The alternator and voltage regulator were removed from the engine and taken to an FAA-certified repair station for bench functional testing. Both units were found to function normally when tested as separate units. The FAA inspectors reported that they then contacted the present holder of the airship's type certificate, American Blimp Corporation of Hillsboro, Oregon. The company's owner provided a written statement. The pilot had contacted the company and said he had been having electrical problems, specifically, keeping the battery sufficiently charged. The pilot had a second battery and would put a freshly-charged one in the blimp prior to flight while the one removed was put on a charger. American Blimp Corporation provided a factory mechanic to assist the FAA inspectors in another examination of the electrical system on March 10, 1995. During the examination, a battery system short was detected at the battery wires which was traced to a short in the starter switch. When the panel was removed to get to the starter switch, the hot lead slipped off the switch post. As the area was examined, the inspectors noted that other wires were marked with duct tape pieces and attached to the switch with push-on style connectors. The installation was not in accordance with factory procedures or with those noted in the maintenance manual. The original factory-installed switch uses screw connectors. The pilot sustained fatal injuries in the accident and an autopsy was conducted by the Alameda County Coroner with specimens retained for toxicological examination. The results of the toxicological tests were negative for alcohol and all screened drug substances. THE BLIMP HAD A HISTORY OF UNRESOLVED ELECTRICAL SYSTEM CHARGING PROBLEMS. THE GROUND CREW WERE GIVEN RIDES AFTER THE LAST REVENUE FLIGHT. AS ONE OF THE GROUND CREW GOT IN FOR HIS RIDE, HE ACCIDENTLY MOVED THE MIXTURE AND KILLED THE ENGINE. THE PILOT RESTARTED THE ENGINE THEN SAID HE HAD A LOW-BATTERY WARNING LIGHT, BUT THOUGHT HE HAD ENOUGH OF A CHARGE TO MAKE ONE MORE CIRCUIT. THE PASSENGER SAID THE LOW-BATTERY LIGHT REMAINED ON FOR THE ENTIRE FLIGHT. ON APPROACH, THE PILOT WENT AROUND DUE TO A WIND GUST. ON THE SECOND DOWNWIND, THE VOLTAGE DROPPED TO 4 AND THE PILOT TURNED DIRECTLY TOWARD THE LANDING AREA. AT THAT POINT, THE ELECTRICAL SERVOS WHICH MOVE THE CONTROL SURFACES STOPPED WORKING DUE TO THE LOW VOLTAGE. THE BLIMP HIT THE GRASS SHORT OF THE LANDING ZONE AND BOUNCED ALONG THE GROUND UNTIL IT STOPPED NEAR THE TOP OF A BERM. THE PILOT TOLD THE PASSENGER TO GET OUT AND HOLD THE BLIMP DOWN. THE PASSENGER TRIPPED AS HE GOT OUT AND ROLLED DOWN THE HILL. WHEN HE GOT BACK ON HIS FEET, THE BLIMP WAS RISING WITH THE PILOT HOLDING ON TO A HOLD DOWN RAIL. THE PILOT LOST HIS GRIP AND FELL FROM 200 FEET. POSTACCIDENT TESTS OF THE ELECTRICAL SYSTEM REVEALED THAT A SHORT IN THE STARTER SWITCH WAS CONSTANTLY DRAINING THE BATTERY. THE SWITCH WIRING WAS NOT INSTALLED IN ACCORDANCE WITH FACTORY STANDARDS OR THE MAINTENANCE MANUAL. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1995_LAX95LA121.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, go-around, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
Browse the full corpus — academia portal ↗