37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 684449 |
Time | |
Date | 200601 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : tapa.airport |
State Reference | FO |
Altitude | agl single value : 1200 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : tapa.tower |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
ASRS Report | 684449 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
ASRS Report | 684450 |
Events | |
Anomaly | inflight encounter other |
Independent Detector | aircraft equipment other aircraft equipment : egpws |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | Chart Or Publication Environmental Factor |
Primary Problem | Chart Or Publication |
Situations | |
Chart | airport : tapa.airport |
Narrative:
During final approach to landing in tapa; runway 07; we received an egpws warning for an obstacle. Conditions were day VFR and we were well clear of all terrain and obstacles. The aircraft was approximately 4 mi from the end of the runway at approximately 1200 ft AGL; on the runway centerline and on the correct glide path (2 white 2 red PAPI). There were no charted obstacles in the immediate path and there were no red or yellow obstacles displayed on the nd in the terrain mode. I have spoken to other pilots who have experienced the exact same thing recently going into tapa. I suspect that there is something corrupt in the egpws database as this seems to be happening to too many aircraft that are established within parameters on final approach to tapa runway 07. There are no notes on any of the company or commercial chart pages for tapa stating that approach procedures differ from standard ICAO procedures due to obstacle clearance concerns. Wouldn't there be if you weren't supposed to follow the PAPI's installed for that runway?supplemental information from acn 684450: received terrain and obstacle alerts from egpws on final. Because I was briefed other crews had received this terrain and or obstacle warnings on final to runway 07 at tapa and I was positioned appropriately on final and could clear the approach corridor visually; I continued. Every crew I have talked to that has flown into tapa recently reports similar alerts; warnings; or cautions on final to tapa runway 07. Nothing red showed on egpws display concurrent with warnings.callback conversation with reporter revealed the following information: the reporter stated that he does not know the source of the warnings and does not rule out a spurious annunciation because he cannot see an obstacle in that area. Because his first officer had this experience before and did not remember a pfd warning; they were both anticipating a red or amber pfd warning but in this event; the pfd annunciation did not occur coincidental with the aural alert.
Original NASA ASRS Text
Title: A TRANSPORT CATEGORY ACFT FLT CREW REPORTS AN EGPWS WARNING ON SHORT FINAL TO TAPA; WITH NO CORRESPONDING TERRAIN/OBSTACLES VISIBLE OR DISPLAYED ON THE ACFT'S PFD.
Narrative: DURING FINAL APCH TO LNDG IN TAPA; RWY 07; WE RECEIVED AN EGPWS WARNING FOR AN OBSTACLE. CONDITIONS WERE DAY VFR AND WE WERE WELL CLEAR OF ALL TERRAIN AND OBSTACLES. THE ACFT WAS APPROX 4 MI FROM THE END OF THE RWY AT APPROX 1200 FT AGL; ON THE RWY CTRLINE AND ON THE CORRECT GLIDE PATH (2 WHITE 2 RED PAPI). THERE WERE NO CHARTED OBSTACLES IN THE IMMEDIATE PATH AND THERE WERE NO RED OR YELLOW OBSTACLES DISPLAYED ON THE ND IN THE TERRAIN MODE. I HAVE SPOKEN TO OTHER PLTS WHO HAVE EXPERIENCED THE EXACT SAME THING RECENTLY GOING INTO TAPA. I SUSPECT THAT THERE IS SOMETHING CORRUPT IN THE EGPWS DATABASE AS THIS SEEMS TO BE HAPPENING TO TOO MANY ACFT THAT ARE ESTABLISHED WITHIN PARAMETERS ON FINAL APCH TO TAPA RWY 07. THERE ARE NO NOTES ON ANY OF THE COMPANY OR COMMERCIAL CHART PAGES FOR TAPA STATING THAT APCH PROCS DIFFER FROM STANDARD ICAO PROCS DUE TO OBSTACLE CLRNC CONCERNS. WOULDN'T THERE BE IF YOU WEREN'T SUPPOSED TO FOLLOW THE PAPI'S INSTALLED FOR THAT RWY?SUPPLEMENTAL INFO FROM ACN 684450: RECEIVED TERRAIN AND OBSTACLE ALERTS FROM EGPWS ON FINAL. BECAUSE I WAS BRIEFED OTHER CREWS HAD RECEIVED THIS TERRAIN AND OR OBSTACLE WARNINGS ON FINAL TO RWY 07 AT TAPA AND I WAS POSITIONED APPROPRIATELY ON FINAL AND COULD CLEAR THE APCH CORRIDOR VISUALLY; I CONTINUED. EVERY CREW I HAVE TALKED TO THAT HAS FLOWN INTO TAPA RECENTLY REPORTS SIMILAR ALERTS; WARNINGS; OR CAUTIONS ON FINAL TO TAPA RWY 07. NOTHING RED SHOWED ON EGPWS DISPLAY CONCURRENT WITH WARNINGS.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THAT HE DOES NOT KNOW THE SOURCE OF THE WARNINGS AND DOES NOT RULE OUT A SPURIOUS ANNUNCIATION BECAUSE HE CANNOT SEE AN OBSTACLE IN THAT AREA. BECAUSE HIS FO HAD THIS EXPERIENCE BEFORE AND DID NOT REMEMBER A PFD WARNING; THEY WERE BOTH ANTICIPATING A RED OR AMBER PFD WARNING BUT IN THIS EVENT; THE PFD ANNUNCIATION DID NOT OCCUR COINCIDENTAL WITH THE AURAL ALERT.
Data retrieved from NASA's ASRS site as of January 2009 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.