WPR09LA418 · Cessna 177 B
Cessna 177 B · Accident: fire/smoke (non-impact) while standing
From Chandler Municipal Airport (CHD) to TUC · Tucson, AZ
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR09LA418
- 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
Cessna 177 B
- Aircraft type
- Cessna 177
- 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
- N30715
- Operator
- Sonoran Wings
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Chandler Municipal Airport (CHD), Chandler, AZTo TUC · Tucson, 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
- Standing · engine(s) not operating
- 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
- Destroyed
Cause areas
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After attempting to start the engine four times without success the pilot called his flight instructor, who advised him to use the "flooded" procedure. Following an unsuccessful start attempt using the flooded procedure, the pilot was going through the checklist when he heard a "pop" sound, then observed dark smoke coming from the engine. The pilot then exited the airplane while first responders extinguished the fire. The pilot stated that a second fire erupted in the engine compartment and "...the airplane's engine started and the propeller started spinning." The airplane was subsequently destroyed by fire damage. Examination of the wreckage by a Federal Aviation Administration inspector revealed extensive fire damage to the engine and forward part of the airframe, which precluded determination of the reason for the fire.
Probable cause
An on-ground fire in the engine compartment for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09LA418
- Event ID
- 20090827X22600
- Case number
- WPR09LA418
- 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: 0949e46bd4b35c7a83061743abd7449e55618a2a8e5349240c456a75ee5a42b8; retrieved 2026-09-15T12:51:12.082Z.