37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 682500 |
Time | |
Date | 200512 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : skbo.airport |
State Reference | FO |
Altitude | msl single value : 12500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : skbo.artcc |
Operator | common carrier : air carrier |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : intermediate altitude climbout : initial |
Route In Use | departure sid : guy |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
ASRS Report | 682500 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | conflict : airborne critical |
Independent Detector | aircraft equipment : tcas other flight crewa |
Resolutory Action | flight crew : took evasive action |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Aircraft Airport ATC Human Performance |
Primary Problem | Ambiguous |
Narrative:
We had been cleared on the guy 5/zip transition to 17000 ft departing out of skbo with no traffic advisories from skbo departure. On climb out passing 12500 ft; I noticed traffic on TCAS showing +10 above directly on our course coming opposite direction. The TCAS picked up an advisory moments later then the computer quickly went from amber advisory to red resolution commanding a 'monitor vertical speed;' reducing our climb rate to approximately 300 FPM climb when a second later the target began a descent into us and the TCAS began shouting at the top of its lungs; 'descend;' with master warnings. We were in broken IMC conditions so we started a descent while the target followed us down into the mountainous terrain of skbo. I radioed skbo what we were doing trying to find out about the traffic. Skbo stated there was no traffic on their scope and we never got a visual in the broken clouds. After we 'cleared' the traffic; skbo informed us that the previous aircraft departing reported the same event and also dived to avoid a collision that radar on the ground never indicated. It would have been nice to know about that from skbo. Is someone able to project a false TCAS signal to intentionally create conflicts? We told skbo to let the following aircraft know but he still thought there was no problem.callback conversation with reporter revealed the following information: reporter noted that the TCAS was operated in the 40 NM range and that the target was first detected 40 NM ahead of their aircraft. From that point the progression was just 'like in the simulator' because very quickly the aircraft went yellow; red; then RA commands issued. This crew speaks spanish and listened to the previous departing aircraft; an MD80; report a similar event even though ATC repeatedly stated they had no traffic in the area. The reporter believes the skbo radar controllers are believable based on previous work with them. At no time during this event did the crew sight the target even though the scattered to broken clouds should have permitted it to be seen. The reporter questions whether an externally positioned person could electronically manipulate a target picked up by an aircraft. This target exhibited very deliberate behavior but reporter wonders whether it really existed. He doubts that an internal ped could have caused the interference because of the previous aircraft's report.
Original NASA ASRS Text
Title: A B767-300 RECEIVED AN RA AT 12500 FT DEPARTING SKBO. THE DETECTED TFC WAS INITIALLY 1000 FT ABOVE AND CAME WITHIN 100 FT BEFORE DISAPPEARING BEHIND THE ACFT. THE TARGET WAS NEVER VISUALLY DETECTED.
Narrative: WE HAD BEEN CLRED ON THE GUY 5/ZIP TRANSITION TO 17000 FT DEPARTING OUT OF SKBO WITH NO TFC ADVISORIES FROM SKBO DEP. ON CLBOUT PASSING 12500 FT; I NOTICED TFC ON TCAS SHOWING +10 ABOVE DIRECTLY ON OUR COURSE COMING OPPOSITE DIRECTION. THE TCAS PICKED UP AN ADVISORY MOMENTS LATER THEN THE COMPUTER QUICKLY WENT FROM AMBER ADVISORY TO RED RESOLUTION COMMANDING A 'MONITOR VERT SPD;' REDUCING OUR CLB RATE TO APPROX 300 FPM CLB WHEN A SECOND LATER THE TARGET BEGAN A DSCNT INTO US AND THE TCAS BEGAN SHOUTING AT THE TOP OF ITS LUNGS; 'DSND;' WITH MASTER WARNINGS. WE WERE IN BROKEN IMC CONDITIONS SO WE STARTED A DSCNT WHILE THE TARGET FOLLOWED US DOWN INTO THE MOUNTAINOUS TERRAIN OF SKBO. I RADIOED SKBO WHAT WE WERE DOING TRYING TO FIND OUT ABOUT THE TFC. SKBO STATED THERE WAS NO TFC ON THEIR SCOPE AND WE NEVER GOT A VISUAL IN THE BROKEN CLOUDS. AFTER WE 'CLRED' THE TFC; SKBO INFORMED US THAT THE PREVIOUS ACFT DEPARTING RPTED THE SAME EVENT AND ALSO DIVED TO AVOID A COLLISION THAT RADAR ON THE GND NEVER INDICATED. IT WOULD HAVE BEEN NICE TO KNOW ABOUT THAT FROM SKBO. IS SOMEONE ABLE TO PROJECT A FALSE TCAS SIGNAL TO INTENTIONALLY CREATE CONFLICTS? WE TOLD SKBO TO LET THE FOLLOWING ACFT KNOW BUT HE STILL THOUGHT THERE WAS NO PROBLEM.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR NOTED THAT THE TCAS WAS OPERATED IN THE 40 NM RANGE AND THAT THE TARGET WAS FIRST DETECTED 40 NM AHEAD OF THEIR ACFT. FROM THAT POINT THE PROGRESSION WAS JUST 'LIKE IN THE SIMULATOR' BECAUSE VERY QUICKLY THE ACFT WENT YELLOW; RED; THEN RA COMMANDS ISSUED. THIS CREW SPEAKS SPANISH AND LISTENED TO THE PREVIOUS DEPARTING ACFT; AN MD80; RPT A SIMILAR EVENT EVEN THOUGH ATC REPEATEDLY STATED THEY HAD NO TFC IN THE AREA. THE RPTR BELIEVES THE SKBO RADAR CTLRS ARE BELIEVABLE BASED ON PREVIOUS WORK WITH THEM. AT NO TIME DURING THIS EVENT DID THE CREW SIGHT THE TARGET EVEN THOUGH THE SCATTERED TO BROKEN CLOUDS SHOULD HAVE PERMITTED IT TO BE SEEN. THE RPTR QUESTIONS WHETHER AN EXTERNALLY POSITIONED PERSON COULD ELECTRONICALLY MANIPULATE A TARGET PICKED UP BY AN ACFT. THIS TARGET EXHIBITED VERY DELIBERATE BEHAVIOR BUT RPTR WONDERS WHETHER IT REALLY EXISTED. HE DOUBTS THAT AN INTERNAL PED COULD HAVE CAUSED THE INTERFERENCE BECAUSE OF THE PREVIOUS ACFT'S RPT.
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.