AN ACR B767 FLC HAS A SERIOUS ELECTRICAL SHORT WITH SMOKE BEHIND THE FO'S GLARESHIELD. THE FLC DECLARES AN EMER AND DIVERTS YQY FOR A SAFE OVERWT LNDG WITH NO EVAC AS THE SMOKE HAD DISSIPATED.

Date: 1996-08 · Aircraft: B767 Undifferentiated or Other Model

Anomalies: aircraft-equipment-problem-critical|other-unspecified

Synopsis

AN ACR B767 FLC HAS A SERIOUS ELECTRICAL SHORT WITH SMOKE BEHIND THE FO'S GLARESHIELD. THE FLC DECLARES AN EMER AND DIVERTS YQY FOR A SAFE OVERWT LNDG WITH NO EVAC AS THE SMOKE HAD DISSIPATED.

Narrative

APPROX 1 1/2 HRS INTO OUR FLT AT FL370 THE CAPT AND I; IN THE FO SEAT; SMELLED ELECTRICAL SMOKE AT ABOUT XA10Z. WE WERE 40 NM NE OF SYDNEY; NS. AS WE DONNED OUR OXYGEN MASKS AND GOGGLES; THICK; ACRID SMOKE SUDDENLY POURED FROM BEHIND THE GLARESHIELD ON MY SIDE. IT WAS ACCOMPANIED BY A VERY HOT HEAT CTR THAT HAD THE APPEARANCE OF AN ARC WELDER. IMMEDIATELY I DECLARED AN EMER; AND ASKED MONCTON CTR; 118.6; WHERE THE NEAREST AIRFIELD WAS AND HOW LONG WAS THE RWY. AS SOON AS HE INFORMED ME SYDNEY; CYQY; WAS 40 NM BEHIND US WITH 7000 FT; I STARTED AN EMER DSCNT INITIALLY TO THE L. MONCTON THEN ASKED IF WE COULD TURN R BECAUSE OF A TFC CONFLICT; SO I DID. WE STARTED DOWN ABOUT XA13Z. ABOUT THIS TIME THE EQUIP COOLING OVERHEAT LIGHT ILLUMINATED WHICH RAISED MY CONCERNS THAT WE HAD A FIRE IN THE UNDER-DECK AREA. THE INTL RELIEF OFFICER HAD NOW ENTERED THE COCKPIT AND WAS ASSISTING US. WE ACCOMPLISHED THE CHKLIST FOR THE OVERHEAT AND THEN STARTED LOOKING FOR THE APCH PLATES FOR SYDNEY; WHICH WE COULD NOT FIND. I WAS ABLE TO OBTAIN THE APCH; ARPT AND WX DATA FROM MONCTON. WE COORDINATED WITH THE #1 FLT ATTENDANT THAT WE WOULD LAND IN 15 MINS AND AT THE TIME DID NOT PLAN AN EVAC AS THE SMOKE HAD STARTED TO DISSIPATE AND THE EQUIP COOL LIGHT HAD EXTINGUISHED. WE CAUGHT SIGHT OF THE RWY ABOUT 5000 FT AND SHOT A VISUAL. I HAD TRANSFERRED CTL OF THE ACFT TO THE CAPT AS HE WAS HAVING COM PROB; AND ELECTED TO LET HIM FLY THE APCH AND LNDG. THE LNDG WAS FIRM AT ABOUT 700 FPM DSCNT RATE AND OUR WT WAS 291.3-278 MAX.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.