# NTSB CHI04LA295: Aero Commander Callair A-9B, N7798V, Norton, KS, July 16, 2004 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: July 16, 2004, 18:40 local (23:40 UTC) - Place: Norton, KS - Coordinates: 39.829299, -99.889984 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.8293&lon=-99.8900&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report April 25, 2006 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 60377 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI04LA295 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/60377/pdf - Page: https://openairdocs.org/ntsb/CHI04LA295 ## Probable cause The fire in the area of the fuel line and the unsuitable terrain encountered during an emergency landing by the pilot. Contributing factors were the pole. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Fire, cruise - fuel system,line (cause) - Forced landing, emergency descent/landing - On ground/water collision with object, emergency landing - object - pole (contributing factor) - On ground/water encounter with terrain/water, emergency landing - unsuitable terrain or takeoff/landing/taxi area - encountered, pilot in command (cause) ## Analysis The agricultural airplane received substantial damage on impact with a utility pole and terrain during a forced landing. The airplane was en route to apply chemical to a field when it experienced an in-flight fire after originating from the departure airport located approximately 3 miles from the accident site. Inspection of the airplane revealed that a fuel line exhibited evidence of fire and adjacent lines did not exhibit similar damage. The operator had not been issued a 14 CFR Part 137 certificate. ## Factual narrative On July 16, 2004, at 1840 central daylight time, an Aero Commander Callair A-9B, N7798V, operated and piloted by a private pilot, received substantial damage on impact with terrain and a utility pole during an emergency landing approximately 3 nautical miles northwest of Norton, Kansas. The pilot reported that he had an in-flight fire in the cockpit. Visual meteorological conditions prevailed at the time of the accident. The 14 CFR Part 91 aerial application flight was not operating on a flight plan. The pilot sustained serious injuries. The local flight originated from Norton Municipal Airport, Norton, Kansas, about 1830. According to the on-scene Federal Aviation Administration (FAA) inspector, a witness stated that the airplane had about 100 gallons of chemical in the hopper and full fuel at the time of departure. Witnesses reported that the airplane was descending from a low altitude when it impacted a milo field, sliding 50-60 yards before impacting a powerline pole and bursting into flames. The airplane came to rest approximately 45 degrees to the left of its initial path after impacting the powerline pole. The pilot egressed from the airplane and sustained third degree burns. The 1970 Aero Commander Callair A-9B, serial number 1551, airplane accumulated a total time of 4,340 hours. The airplane was powered by a Lycoming IO-540 engine, serial number L-7741-48. Airplane logbook records show that the last engine inspection was an annual inspection dated April 14, 2004, at a tachometer time of 1,251.1 hours. Inspection of the airplane by the FAA inspector revealed evidence of fire aft of the left hand side of the engine cooling baffling, above the fuel injector pump part number 75567. The inlet fuel line, part number 18586, a steel braided flexible hose from the fire wall to the fuel pump showed evidence of fire. The end of the fuel line that attached to the fuel pump was burned through and the fire sleeve, part number 18685, was charred with patches of white ash at the end of the fire sleeve. The end of the line that attaches to the firewall exhibited a similar condition. The other lines of similar construction in the area of the fire were not burned through. The operator had not been issued a 14 CFR Part 137 certificate. ## Aircraft - Registration: [N7798V](https://openairdocs.org/deregistered/N7798V-2013-05-09), registration cancelled 2013-05-09, S/N 1551, built 1970 (OpenAirDocs) - Reported make and model: Aero Commander Callair A-9B - Registry model: [Aero Commander CALLAIR A-9B](https://openairdocs.org/model/aero-commander-callair-a-9b) (registry code 0144206) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 1551 - Airframe hours: 4340 - Engines: Lycoming IO-540 reciprocating - Damage: Substantial damage - Fire: Both - Flight: Aerial application, Part 91 - Operator: Pilot - Registered owner: John W. Trail - Airworthiness certificate: Special, Restricted (Special) - Last inspection: Annual, April 1, 2004 - Departed: NRN, Norton, KS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 51; injuries: serious; private; airplane ratings: single-engine land; medical: class 3; seat: center; flight hours: 210 total, 35 in this make and model, 60 in the last 90 days ## Weather - Conditions: Visual (VMC), Day - Wind: 40° at 12 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 88 °F, dew point 57 °F - Altimeter: 30.03 inHg - Observed at: HLC, 28 nm away ## Other investigations on N7798V (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB FTW80DPJ25](https://openairdocs.org/ntsb/FTW80DPJ25), Jun 4, 1980: Callair A-9B (N7798V), Ponca City, OK, substantial damage From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.