NTSB CAROL · Event
Event LAX06LA228
Aircraft involved
Probable cause & findings
an electrical fire due to improper wiring of the electrical system by other maintenance personnel.
Factual narrative
On July 10, 2006, at 1724 Pacific daylight time, an experimental amphibious Palmer Seawind 3000, N8025Q, caught fire following an emergency landing on the water near Clear Bay on the Lower Colorado River's main channel of the Lake Havasu National Wildlife Refuge, near Havasu Lake, California. The emergency landing was precipitated by a strong electrical smoke in the cockpit. The water landing was successful, but the airplane was destroyed during the ensuing post impact fire. The pilot/owner operated the airplane as a personal flight under the provisions of 14 CFR Part 91. The private pilot and one passenger were not injured. Visual meteorological conditions prevailed for the flight that departed Lake Havasu City Airport (HII), Lake Havasu City, Arizona, about 1700. No flight plan had been filed. The flight was destined for French Valley (F70), Murrieta/Temecula, California. According to an officer from the United States Fish and Wildlife Service, a call was received from the pilot at 1730 indicating that he had been involved in an accident. In the pilot's written statement he reported that his intent was to do 4 or 5 water landings before heading to F70. On the first landing and takeoff everything was normal. During the takeoff initial climb to conduct another landing, about 150 to 200 feet above the water, he began to smell electrical fumes and immediately observed smoke emanating from the forward right vent of the instrument panel. He immediately turned off the MASTER switch and noted that smoke was still coming from the vent area. He lined up on the river and landed in the shortest time he could. He reduced the power and on short final retarded all of the levers and turned off the magnetos. After landing, he opened the canopy and instructed his son to exit the airplane. As the pilot went to retrieve the fire extinguisher, there was a "fireball of flames." He also exited the airplane. Neither he nor his son was injured. The National Transportation Safety Board investigator-in-charge (IIC) interviewed the pilot. The pilot indicated that he had purchased the airplane in September 2005, and it had been in a maintenance shop for 7 months. He further indicated that a King Global Positioning System (GPS) had recently been installed. He reported that he had been flying the airplane for about 3 months. A Safety Board investigator examined the airplane at Air Transport, Phoenix, Arizona, on October 29, 2006. Two Odyssey Extreme drycell batteries, which were interconnected in a tandem configuration, powered the airplane. The batteries were secured to a wall on the right side nose/storage compartment area. There were two solenoids that the batteries were connected to, a MASTER and a START solenoid. Each battery had their own positive and negative cables that were then connected to the solenoids. The battery compartment had a burn mark on the side that corresponded with the size and position of the negative cable on the right side battery. The right battery cables' protective coverings were burned and melted off. The protective covering for the left battery cables were intact until they passed through the firewall. The Safety Board investigator noted that after the cables passed through the firewall, the positive cable for the right battery had melted together with the negative cable for the left battery. In addition, the cables had sustained thermal damage, with 3 of the 4 cables separated on the cockpit side of the firewall. The fourth cable, the negative cable for the left battery remained continuous. Additional inspection of the airplane's electrical wiring by personnel from Aircraft Engine Reconstruction Specialists, Inc., Prescott, Arizona, revealed that the groundside of the forward 24V battery had been wired to the "hot side" of the START solenoid. This would result in a reverse polarity draw during engine start, and a short would occur anytime the starter was energized. Paperwork obtained from Airmech, Inc., dated August 8, 2006, indicated the company moved both batteries to the right side of the nose and rewired the cables to the batteries and solenoids. According to a representative from Seawind, for the experimental airplanes such as the accident airplane, the requirement was for the installation of one battery positioned on the right side nose storage/compartment area at bulkhead 36. The directions also contained information on how to cover the battery and placement of the MASTER and STARTER solenoids. A basic electrical wiring diagram was provided to kit builders. The amphibious airplane was destroyed in a ground fire following a forced landing. During the takeoff initial climb out, electrical fumes and smoke emanated from the right side portion of the instrument panel. A successful water landing was made; however, a post impact fire consumed the airplane. Examination of the airplane revealed that it was equipped with two batteries that were interconnected with each other and positioned in the right side nose/storage compartment area. Both batteries' cables were connected to a single MASTER solenoid and a single START solenoid. A burn mark was located in the battery compartment that was the size and position of the negative cable for the right side battery. The storage area for the batteries was not damaged; however, the cockpit was consumed in the post impact fire. Further inspection of the airplane's electrical wiring revealed that the groundside of the forward battery had been wired to the hot side of the START solenoid that resulted in a reverse polarity draw during engine start. The protective covering for the wires burned away exposing the wires that then came into contact with each other and started the fire. Recent maintenance work on the airplane included movement of both batteries to the right side, and a rewire of the cables to the MASTER and START solenoids. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2006_LAX06LA228.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, 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 …
- 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.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗