# Incident 20041206030639I: Doug DC1030F, Bangor, ME, December 6, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 6, 2004, 23:21 local time
- Place: Bangor, ME
- Airport: Bangor International
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: Air carrier (Part 121)
- Operator: WRLA
- Location: 44.8074° N, 68.8281° W: Placed by OpenAirDocs at BANGOR INTL (BGR), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=44.8074&lon=-68.8281&mi=10
- Aircraft: N304WL (not matched to a registry record)
- Reported make and model: DOUG DC1030F
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 10,800 total, 570 in this make and model, 128 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20041206030639I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) AS NOTED PER BANGOR, MAINE ATCT: "WORLD AIRWAYS 173, DC-10, WHILE LANDING BANGOR, ME RUNWAY 33, AT 2321 EST, 12-6-04, NUMBER TWO ENGINE CAUGHT FIRE UNDER UNKNOWN CIRCUMSTANCES. AIRCRAFT TAXIED TO TAXIWAY "M" WHERE CFR EXTINGUISHED FLAMES. THERE WERE NO INJURIES TO THE CREW OF THREE. AIRCRAFT DAMAGE TO BE DETERMINED. AIRPORT WAS CLOSED FOR APPROXIMATELY 30 MINUTES WHILE AIRPORT MANAGEMENT CLEARED DEBRIS. HOWEVER, THERE WAS NO IMPACT TO AIR TRAFFIC SERVICES. SUPPLEMENTAL INFO: NOTE: AIRCRAFT WAS ENROUTE FROM BRUSSELS, BELGIUM TO DAYTON, OH AND WAS STOPPING AT BANGOR FOR CUSTOMS AND REFUELING. NOTE: AIR TRAFFIC CONTROL HEARD A LOUD BANG PRIOR TO OBSERVING ENGINE CATCH FIRE." THIS INSPECTOR PROCEEDED TO BANGOR WITH OPERATIONS INSPECTOR, ^PRIVACY DATA OMITT^ AND AIRWORTHINESS INSPECTOR, ^PRIVACY DATA^ ON MORNING OF 12/07/04. UPON ARRIVAL AT BANGOR, MAINE, WE WERE MET BY WORLD AIRWAYS MAINTENANCE TECHNICIAN AT AIRCRAFT. WE WERE INFORMED BY TECH THAT HE HAD NOT STATED ANY SERIOUS TROUBLESHOOTING AS HE WAS PREPARING TO LAUNCH WORLD MD-11 THAT WAS NEXT DOOR (CARGO RETRIEVAL AIRCRAFT) AND WAS WAITING FOR SENIOR WORLD TECHNICIAN TO COME ON SCENE TO ACCOMPANY HIM WITH INSPECTION. THIS INSPECTOR REVIEWED AIRCRAFT MX. LOGBOOK AND OBSERVED THAT ON LOGBOOK PAGE LP224068 "MX. CONTROL REQUEST NO. 2 ENGINE VAPOR VENT SOLENOID VALVE BE REPLACED" THIS INSPECTOR DOES NOT KNOW AT THIS TIME IF THIS IS A RELATED INCIDENT. OPERATIONS INSPECTOR OBSERVED THAT FUEL USED GAUGES IN COCKPIT READ AS REPORTED: #1 GAUGE 46940/#2 GAUGE 49620/#3 GAUGE 45740. LARGE DISCREPANCY NOTED BETWEEN NUMBER 2 GAUGE AND #1 & #3. OTHER MAINTENANCE WRITE UP IN LOGBOOK RELATED TO INCIDENT: "L1 DOOR OPENED PNEUMATICALLY & SLIDE DEPLOYED EMERGENCY EGRESS" PROCEEDED TO CONTACT OFFICE MANAGER IN PORTLAND, MAINE TO INFORM HIM OF EMERGENCY EGRESS. OFFICE MANAGER IN TURN NOTIFIED NTSB OF EGRESS. VARIOUS SECTIONS OF #2 ENGINE COWL APPEARED TO HAVE SINGED AREAS SURROUNDING THE BOTTOM SECTION OF THE COWL AND ALONG VARIOUS AREAS OF THE TAIL OF THE EMPENNAGE. A SHORT TIME LATER WORLD SENIOR TECH SHOWED AT AIRCRAFT TO TRY AND ESTABLISH WHAT THE CAUSE OF THE INCIDENT WAS. WEATHER WENT DOWN IN BANGOR DUE TO SNOWSTORM. TALKED TO SENIOR TECH ON MORNING OF 12/8 BY TELEPHONE AND WAS INFORMED THAT HE COULD GET FAN COWL OPEN BUT COULD NOT OPEN CORE COWL. HE STATED THAT HE HAD ACCOMPLISHED A FUEL PRESSURE CHECK AND THIS TIMEYOULD NOT LOCATE ANY OBVIOUS FUEL LEAK. HE ALSO MENTIONED THAT COWLING WAS WARPED OUT OF SHAPE AND THAT HYDRAULIC LINE THAT IS USED TO PUMP COWL OPEN HAD MELTED. SENIOR TECH HAS BEEN NOTIFIED BY HIS D.O.M. NOT TO GO ANY FURTHER INTO INSPECTION, BECAUSE NTSB IS DUE ON SCENE SOME TIME IN P.M. SHORTLY AFTER THIS INSPECTOR WAS CONTACTED BY WORLD AIRWAYS D.O.M. WHO STATED THAT ON 12/8 A DELTA STRUCTURE INSPECTION SPECIALIST WOULD BE ON SCENE WITH NTSB TO DETERMINE IF #2 ENGINE UPPER NACELLE STRUCTURE HAD SUSTAINED ANY DAMAGE DURING FIRE. RETURNED TO BANGOR ON 12-9-04. NTSB AND FAA ACCIDENT INVESTIGATIVE BRANCH NOW IN CHARGE OF INVESTIGATION.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.