ACFT STRIKES TREE DURING INST APCH.

1995-01 · NASA ASRS report 295602

Date: 1995-01 · Aircraft: DC-8 62

Anomalies: inflight-event-encounter-cftt-cfit|inflight-event-encounter-weather-turbulence|other-unspecified

Synopsis

ACFT STRIKES TREE DURING INST APCH.

Narrative

I WAS WORKING AS CAPT ON A CARGO CHARTER FROM MIAMI TO MANAUS; BRAZIL (SBEG). ABOUT 180 MI OUT OF SBEG I REQUESTED ARPT CONDITIONS IN ORDER TO PLAN THE APCH AND BRIEF THE CREW. WE WERE GIVEN AS I REMEMBER; SCATTERED 800 FT; 1000 METERS; TEMP 28 DEGS C; WINDS 120 AT 6 KTS AND 1010 MB. I ASKED MY FO TO ASK THE REASON FOR REDUCED VISIBILITY. AFTER ASKING SEVERAL TIMES THEY FINALLY ANSWERED 'RAIN.' HAVING LANDED THERE MANY TIMES IN RAIN IN THE PAST; I THOUGHT I HAD A PRETTY GOOD IDEA OF WHAT TO EXPECT. THERE WERE SEVERAL LAYERS OF CLOUDS AND I REMEMBER I THOUGHT I SAW A BUILDUP OUT TO THE R OF MY COURSE LINE BUT NOTHING SHOWED UP ON MY WX RADAR. THE WX RADAR HAD BEEN WRITTEN UP SEVERAL TIMES IN THE PAST AS PAINTING VERY WEAK. I PLANNED TO HAND FLY THE ACFT SINCE ON AUTOPLT IN TURNS IT WOULD GO TO 35 DEGS OF BANK AND DISCONNECT. IN MY BRIEFING I INSTRUCTED MY FO THAT APCHING THE VOR I WOULD HAVE HIM TUNE ME TO THE ILS AND KEEP HIMSELF ON THE VOR TO IDENT STATION PASSAGE. THE VOR IS CO-LOCATED WITH THE OM AND IS 3.5 MI SO I DIDN'T WANT TO RELY ON IT AND I DID WANT TO VERIFY PASSING THE VOR AND XCHK GS ALT. WE WERE INITIALLY CLRED TO DSND TO FL190 THEN TURNED OVER TO MANAUS APCH WHO THEN CLRED US TO FL040. APCHING THE VOR WE WERE CLRED TO 2000 FT AND CLRED STRAIGHTIN ILS RWY 10. KNOWING THE APCH IS SHORT AND THINGS HAPPEN VERY FAST; I STARTED CONFIGURING EARLY AND WAS ESTABLISHED ON THE ILS OUTSIDE THE VOR. WX INFO WAS GIVEN A COUPLE MORE TIMES VARYING 'SCATTERED' 600 FT TO 800 FT AND VISIBILITY WAS GIVEN AS 800 METERS; MINIMUMS FOR THE APCH. RIGHT AT THE VOR I HEARD VISIBILITY RPTED AS 500 METERS BUT SINCE WE WERE ESTABLISHED I DECIDED TO CONTINUE. I COULD SEE NO REASON NOT TO AND WE HAD PLENTY OF FUEL TO MISS AND HOLD FOR A WHILE. XING THE VOR APCH CTL SAID CONTACT TWR. THE FO; VERY NEW IN THE ACFT AND COMPANY; CHANGED TO TWR AND CALLED; GOT NO ANSWER; CALLED AGAIN AND AFTER WHAT SEEMED LIKE A HUGE PAUSE; FINALLY WAS GIVEN WINDS 120 DEGS AT 6 KTS; CLRED TO LAND. WHILE ALL THIS WAS GOING ON; I SAW MY GS NEEDLE BOUNCE BUT IT CAME RIGHT BACK IN AGAIN AND NEVER SHOWED AN OFF FLAG. BY THIS TIME WE WERE GETTING PRETTY LOW ON THE APCH AND ENTERED HVY RAIN; LIGHT AND OCCASIONAL MODERATE TURB. THE FO WAS JUST FINALLY ABLE TO RETUNE HIS NAV TO THE ILS. AS THE FO WAS DOING ALL THIS I WAS HAND FLYING THE APCH AND I REMEMBER SEEING THE SPD INCREASING AND ADJUSTING. AT THE TIME I DIDN'T THINK MUCH OF IT PROBABLY BECAUSE I HAD MY HANDS FULL BUT IN HINDSIGHT HAD I NOT MADE ADJUSTMENTS FOR IT I THINK THE SPD INCREASE WOULD HAVE BEEN SIGNIFICANT. I THEN HEARD THE GPWS SOUND 'MINIMUMS' AND KNOWING MY BAROMETRIC ALT WAS STILL WELL ABOVE MINIMUMS; I KNEW SOMETHING WAS WRONG BUT COULDN'T TELL WHAT. I ALSO REMEMBER AT THIS POINT; ALL AT THE SAME TIME; THE SPD BEGAN BLEEDING OFF I STARTED ADDING PWR. I DIDN'T WANT TO GET TOO FAST BECAUSE THE RWY WAS SHORT AND WET AND WE WERE AT MAX LNDG WT BUT WITHIN WET LNDG LIMITS. THE GS BECAME ERRATIC THEN WENT FULL UP DEFLECTION. I CAUGHT A GLIMPSE OUTSIDE AND SAW TREE TOPS; WENT TO FIREWALL PWR AND PITCHED UP. ON THE MISS WE CLIPPED THE TOPS OF SOME TREES AND FLAMED OUT #4 ENG. I REMEMBER DURING THE MISS SEEING SOME LIGHTNING AND THAT WAS THE FIRST CLUE I HAD THAT THE RAIN THEY WERE RPTING WAS VERY HVY AND PART OF A TSTM OVER THE FIELD. NOTHING ABOUT TSTMS WAS EVER RPTED TO ME. I ELECTED TO HOLD AND AWAIT BETTER WX; DECLARED AN EMER; REQUESTED EMER EQUIP SINCE I DIDN'T KNOW FULL EXTENT OF DAMAGE; THEN AFTER THE WX IMPROVED WE LANDED WITHOUT FURTHER INCIDENT. NO EMER EQUIP WAS IN SIGHT WHEN WE LANDED. IN HINDSIGHT; I THINK THE REASON FOR THE INCIDENT WAS WIND SHEAR/MICROBURST. THE SYMPTOMS WERE THERE; HOWEVER; AT THE TIME I HAD NO KNOWLEDGE OF ANY CONVECTIVE ACTIVITY; LET ALONE A TSTM OVER THE FIELD. CONTRIBUTORS WERE UNDERSTATED WX; WX RADAR THAT WAS VERY WEAK; A LARGE DISCREPANCY BTWN RADAR AND BAROMETRIC ALTIMETERS; A GS THAT BECAME ERRATIC AND COMPLICATING ALL THIS; IS THE SHORT DISTANCE FROM THE VOR/OM TO MISSEDAPCH AND CHANGING TO TWR AT THE VOR. I'VE LEARNED THROUGH THIS INCIDENT THAT THE MIL SENSE OF MISSION ACCOMPLISHMENT IS STILL THERE. I THOUGHT I HAD GOTTEN RID OF IT THROUGH THE YRS BUT IT'S STILL THERE AND FROM NOW ON ANY TIME THINGS DON'T FEEL JUST RIGHT; IT'S TIME TO GAR AND REGROUP. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: HIS CREW MEMBERS WERE ALL LOW TIME PLTS; THUS VERY INEXPERIENCED. THE FE WAS NOT PLT QUALIFIED. WAS VERY DILIGENT AND HARD WORKING; BUT HAD NO INST EXPERIENCE. FO JUST HAD ENOUGH TIME TO HAVE A COMMERCIAL AND INST RATING. RPTR CAPT WAS NOT INFORMED THAT A TSTM WAS OVER THE ARPT. THE METEOROLOGIST WAS NOT ON DUTY AND WX INFO HAD NOT CHANGED DURING THE COURSE OF THE STORM. THE ALTIMETER SETTING WAS 4-6 HRS OLD. THE GS HAD A FEW BUMPS IN IT; BUT IT SEEMED ACCEPTABLE TO THE RPTR. HE FOLLOWED THE GS DOWN; THEN WHEN IT WENT FULL SCALE UP SUDDENLY; HE APPLIED PWR; SAW A TREE AHEAD OF THEM AND ROTATED TO MAX ANGLE UP. HE NEVER SAW THE RWY OR RWY ENVIRONMENT; JUST THE TREE THAT HE HIT AND HIS IMMEDIATE REACTION AS HE ROTATED THE NOSE UP WAS THAT; 'WE WERE NOT GOING TO MAKE IT.' #4 ENG WAS STRUCK BY THE TREE; AND WAS DESTROYED BY THE INGESTION OF THE BRANCHES. DAMAGE WAS SEVERE SO IT IS THOUGHT THAT TREE WAS A MAHOGANY TREE. THE TREE WAS HIT AT AN ALT OF 600 FT BUT FIELD ELEVATION IS APPROX 250 FT. SINCE THE TREE WOULD NOT BE 350 FT TALL BUT IN ALL PROBABILITY 100 FT IN HT; THE DIFFERENCE IS EXPLAINED BY THE NON CURRENT ALTIMETER SETTING. RPTR FEELS THE ILS HE FOLLOWED PRESENTED A FALSE GS. THERE HAVE BEEN MANY RUMORS TO THE EFFECT THAT THE GS WAS FREQUENTLY FALSE IN HVY RAIN. GS WAS TESTED OKAY IN GOOD FLT CONDITIONS; NO TESTING WAS DONE IN HVY RAIN. THE ACR COMPANY HAS NOW CHANGED THE MINIMUMS TO 300 FT HIGHER THAN PRIOR TO THIS EVENT. THE NTSB HAS INVESTIGATED THIS OCCURRENCE AND HAS DECLARED IT AN INCIDENT. NONE OF THE FLC WERE DISCIPLINED AS A RESULT OF THIS INCIDENT. CALLBACK CONVERSATION WITH RPTR ACN #295321 REVEALED THE FOLLOWING INFO: THE RPTR WAS FLYING THE DC-8-62 FOR AN ACR THAT HAS BEEN SHUT DOWN BY THE FAA FOR MAINT SHORTCOMINGS. THE CAPT WAS ON THE GS WHEN HE HIT THE TREES. THE #4 ENG WAS DAMAGED BEYOND REPAIR AND WAS LEFT IN MAO. THE ACFT FLEW HOME ON A 3 ENG FERRY. AN ACI FLEW INTO MAO WITH ANOTHER CREW RECENTLY THAT WOULD HAVE FLOWN INTO THE GND HAD THEY STAYED ON THE GS. THE RPTR HAS HEARD NOTHING FROM THE FAA SINCE A FACT FINDING SESSION. HE BELIEVES THAT THEY WERE EXONERATED. THE CAPT IS ALREADY FLYING FOR ANOTHER ACR.

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

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.