FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10FA264 · Piper PA-28-161

26 May 2010 · Chandler, AZ, United States

Chandler Air Service Piper PA-28-161 · Accident: fire/smoke (non-impact) during initial climb

From Chandler Municipal Airport (CHD) to Chandler Municipal Airport (CHD)

Report a problem

Event

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

Piper PA-28-161

Aircraft type
Piper PA-28
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
N4122T
Onboard fatalities
Unknown
Route
From Chandler Municipal Airport (CHD), Chandler, AZTo Chandler Municipal Airport (CHD), Chandler, AZ
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
Initial climb
Defining eventThe 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
Fire/smoke (non-impact)
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

  • Aircraft › Aircraft handling/service
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The certificated flight instructor (CFI) and private pilot were performing touch-and-go practice takeoff and landings. When the airplane was turning to the crosswind leg of the traffic pattern they began to see smoke in the cockpit, which was likely coming through the defroster vents. With the airplane about 1,600 feet mean sea level, the CFI assumed authority of the controls and declared an emergency to the tower air traffic controller. Within several seconds the smoke became thick in the cabin, and the CFI banked the airplane right with the intent of landing on the closet runway. The smoke in the cockpit became so thick that the CFI lost visual reference outside. He flared the airplane and it touched down hard. After the airplane came to a stop, the CFI and the private pilot exited. A review of the airplane maintenance logbooks revealed that the last annual inspection was completed 2 days prior to the accident. According to the records, the airplane had accrued approximately 4 additional flight hours since that inspection. An examination of the firewall revealed that its left side had a white coloration which turned to a black soot color on the right side, consistent with the fire originating on the left side of the engine. The fuel line leading from the engine driven fuel pump to the carburetor was found disconnected at the fuel pump. There was no visible impact damage to the “B” nut on the line or to the fitting on the fuel pump, indicating the line was not connected at the time of impact. Based on this evidence, it is likely that the “B” nut on the line was not properly tightened, which allowed it to back off due to normal engine vibration, resulting in the line disconnecting during the flight. Pressurized fuel from the fuel pump then sprayed onto the left side of the exhaust system and ignited. The engine manufacturer recommended that the fuel line “B” nut torque should be 35 in-lbs.

Probable cause

Failure of the maintenance personnel to ensure adequate torque of a fuel line fitting, which resulted in an in-flight fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10FA264
Event ID
20100526X40856
Case number
WPR10FA264
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: c7491b6f02172fe5b1adf132f7aaf6f12c04201d6760896cb32ab620e5e9751d; retrieved 2026-09-15T14:14:26.935Z.