NTSB CAROL · Event
Event ERA10LA210
Aircraft involved
Probable cause & findings
A fire of undetermined origin behind the left instrument panel.
Factual narrative
On April 5, 2010, at 1233 eastern daylight time (EDT), a Beech 35-A33, N156J, was substantially damaged after catching fire immediately following a, rejected takeoff at Allegheny County Airport (AGC), Pittsburgh, PA. The airplane sustained substantial damage to the fuselage. The private pilot/owner and certificated flight instructor (CFI) were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the local instructional flight. The flight was conducted under the provisions of 14 Code of Federal Regulations Part 91. In an interview with the Safety Board, the private pilot stated that the purpose of the flight was for an insurance required proficiency check. He further stated that the CFI had flown the airplane earlier in the day in the local area and had performed two takeoff and landings. After the CFI returned both pilots went to lunch and upon their return, they performed a preflight inspection started the engine, received weather information from the automated terminal information system (ATIS), and then called ground control for taxi clearance. After performing the pre-takeoff checklist in the run-up area for runway 28, the pilot detected a smell but could not confirm what he smelled. After clearance for takeoff was received from the air traffic control tower and takeoff power was applied, the pilot smelled and visually confirmed smoke coming from the instrument panel area. He immediately aborted the takeoff at a speed no greater than 20 knots, and exited the runway at the next taxiway. After shutting off the master and alternator switches, the smoke continued to emanate from the instrument panel. The pilot shut down the engine and both occupants exited the airplane onto the taxiway. They attempted to extinguish the fire with a hand held fire extinguisher that was obtained from a first response vehicle. The CFI observed the exterior paint begin to blister on the left side of the airplane near the area between the instrument panel and firewall. The Airport Rescue and Fire Fighting personnel arrived and extinguished the fire within a few moments; however, the airplane cabin area had been consumed by fire. The pilot also stated that the airplane was owned by the Pittsburg Institute of Aeronautics, and the college purchased the airplane approximately six months prior to the accident. The airplane logbooks had been lost prior to the purchase of the airplane and the college attempted to reconstruct the logbooks. The college completed all of the required annual inspections on the airplane. He also mentioned that the college had not completed any work on the avionics or wiring of the airplane since they purchased it. According to the pilot and Federal Aviation Administration (FAA) records, he held a private pilot certificate with ratings for airplane single-engine, multiengine land, and instrument airplane. His most recent FAA third-class medical certificate was issued on May 11, 2009, and at the time of the accident, he had accrued 387 total hours of flight experience and no hours in the accident airplane make and model. According to FAA records, the CFI held an airline transport pilot certificate with a rating for airplane single-engine land, a commercial pilot certificate with ratings for airplane multiengine land, rotorcraft-helicopter, glider, and lighter-than-air free balloon, and a flight instructor certificate with ratings for airplane single-engine, multiengine, instrument airplane, and glider. His most recent FAA second-class medical certificate was issued in April 2009, and at that time he reported 25,000 total hours of flight experience. The airplane was a Beech 35-A33 manufactured in 1961. It was equipped with a Continental Motors IO-470-J series engine and a Hartzell propeller. It was a high performance, all-metal, low-wing, single-engine cantilever monoplane with fully retractable tricycle landing gear. The 1253 recorded weather observation at AGC, included winds from 250 degrees at 10 knots with gusts of 25 knots, broken clouds at 4,900 feet and 6,000 feet above ground level, 10 miles visibility, temperature 23 degrees C, dew point 12 C, and an altimeter setting of 30.02 inches of mercury. The airport has two crossing runways designated 10/28 and 13/31. The accident flight was departing off of runway 28 which was a 6,501-foot-long and 150-foot-wide concrete runway. Taxiway A5 was located approximately 350 feet from the beginning of the accident flight takeoff roll. The sections of the airplane consumed by fire were aft of the firewall including the cabin area and roof structure. Examination of the wreckage by the FAA discovered that the source of the fire began on the left side of the instrument panel, in the vicinity of the communication radios, circuit breakers, and electrical bus bar. Communiqué No. 116 provided by Hawker Beechcraft Corporation dated June 2008 "ATA24 Electrical Wire Chafing Protection" states in part "Chafing can lead to failed components, inadvertent operation of equipment and the potential for smoke and fire...the factory configuration requires wire bundle protection adjacent to the fuel tube assembly by use of nylon spiral wrap on earlier airplanes or continuous Varglas sleeving on later airplanes...chaffing reports from three main areas; under the instrument panel, in the engine compartment next to the battery box and wiring routed close to fluid tubes. The area under and forward of the instrument panel not only has the greatest concentration of wiring but also has moving components that can damage improperly secured wiring in a very short period of time...there are multiple locations throughout the airplane where wiring and wire bundles are in close proximity to fluid lines where proper security and protection are important to minimize the potential for chafing damage...periodic inspection of wiring is required at each 100 hour or Annual inspection for proper routing and security." According to an email provided by the mechanic, the only maintenance done to the avionics was replacing the altitude encoder. He could not verify if the wires were protected by the sleeving or the wrap and also stated he had not seen the Communiqué before. During the takeoff roll, the pilot smelled and saw smoke emanating from the instrument panel. He aborted the takeoff, exited the runway, and shut off the master and alternator switches. The smoke continued to emanate from the instrument panel so the pilot elected to shutdown the engine and both occupants exited the airplane. Paint blistering was observed on the left side of the airplane in the vicinity of the instrument panel. The cabin area and the roof structure were consumed by fire, resulting in substantial damage to the airplane. The pilot stated that he purchased the airplane approximately six months prior to the accident, but the airplane and engine logbooks were lost prior to the purchase. After the pilot purchased the airplane, it was inspected in accordance with regulations, but no work was performed on the avionics or wiring other than replacing the altitude encoder. Two years prior to the accident, the manufacturer issued a communiqué that required an inspection for wire chaffing after any maintenance work, and during an annual inspection with special emphasis on examining the areas with considerable amount of movement. It further stated that the area between the instrument panel and the firewall not only had the greatest concentration of wiring, but also had moving components that could damage improperly secured wiring in a very short time. A postaccident inspection by a Federal Aviation Administration inspector revealed that the area of the origin for the fire was the left forward section of the instrument panel, in the vicinity of the communication radios, circuit breakers, and electrical bus bar. The exact source of the fire could not be determined. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
Verbatim from NTSB's published report. Source file
NTSB_2010_ERA10LA210.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 (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 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…
- 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.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗