37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 634215 |
Time | |
Date | 200410 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : tjsj.airport |
State Reference | PR |
Altitude | msl single value : 600 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : tjsj.tower |
Operator | common carrier : air carrier |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : ils 10 |
Flight Phase | descent : approach |
Route In Use | approach : instrument precision arrival other |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : tjsj.tower |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Route In Use | approach : traffic pattern |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
ASRS Report | 634215 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
ASRS Report | 634216 |
Events | |
Anomaly | conflict : airborne critical non adherence : published procedure non adherence : required legal separation other anomaly other |
Independent Detector | aircraft equipment : tcas other flight crewa other flight crewb |
Resolutory Action | flight crew : executed go around |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Chart Or Publication FAA Flight Crew Human Performance Airspace Structure Airport ATC Human Performance |
Primary Problem | Airspace Structure |
Situations | |
Airspace Structure | class c : tjsj.c class d : tjsj.d |
Chart | airport : tjsj.airport approach : tjsj bridge visual |
Narrative:
Approaching sju our flight was cleared for the ILS runway 10 to the lagoon visual approach, cleared to land on runway 8. We were advised of traffic south of the airport on right base to runway 10 on a visual approach. I do not remember if we reported the other traffic in sight on initial advisory. However, we did have the other aircraft in sight at all times. As we approached the airport I advised the first officer (PF) that the traffic appeared to be converging and if it became necessary to go around to avoid traffic, to offset to the north away from the traffic. At somewhere around 500 ft the traffic was in my opinion too close to continue the approach. TCASII gave a traffic alert at the same time and we executed a go around. Return to the airport was normal with about a 10 min delay. After landing the tower queried us as to the reason for the go around. I replied 'inadequate separation, TCASII alert and 2 airplanes occupying the same airspace at the same time.' the tower asked us to call after parking. When I talked to the tower cabin attendant, they wanted to know the reason for the go around, as I cited inadequate separation. I replied it may have been within their requirements, but I felt it was too close for us and we elected to go around. He asked if we had the other traffic in sight when advised. I said we did, but as the traffic converged, it didn't look safe to continue, so we went around. The tower asked if we had done this type of approach before. I stated I had and have even been the aircraft on the south side to runway 10. The tower implied they were happy with the answers. My safety concerns with these approachs are as follows: at sju, the bridge visual to runway 10 and the lagoon visual to runway 8 are converging approachs requiring low altitude maneuvering below 500 ft. Aircraft approaching from the south on the bridge visual are required to make a 90 degree right turn to final while aircraft on the lagoon visual are required to make a left turn about 20 degrees. Final approach courses of these 2 runway intersect approximately 3000 ft from the approach end of the runways. The possibility of an aircraft turning to runway 10 overshooting final is high. The maneuvering also puts both aircraft belly to belly in such a position that pilots will lose visual contact with the other at low altitude. I recommend that separation be given to aircraft to ensure that approachs are staggered enough to ensure an overshoot is not catastrophic. Supplemental information from acn 634216: this presented itself visually by constant bearing and decreasing range to traffic (a turboprop). Several passenger thanked us after landing for moving away from traffic that appeared to be very close in their estimation.
Original NASA ASRS Text
Title: DURING A VISUAL APCH TO RWY 8 A B757-200 FLT CREW PERFORMS A GAR WHEN TFC SEPARATION FROM OTHER TFC ON A VISUAL TO RWY 10 APPEARS TO BE TOO CLOSE TO SJU.
Narrative: APCHING SJU OUR FLT WAS CLRED FOR THE ILS RWY 10 TO THE LAGOON VISUAL APCH, CLRED TO LAND ON RWY 8. WE WERE ADVISED OF TFC S OF THE ARPT ON R BASE TO RWY 10 ON A VISUAL APCH. I DO NOT REMEMBER IF WE RPTED THE OTHER TFC IN SIGHT ON INITIAL ADVISORY. HOWEVER, WE DID HAVE THE OTHER ACFT IN SIGHT AT ALL TIMES. AS WE APCHED THE ARPT I ADVISED THE FO (PF) THAT THE TFC APPEARED TO BE CONVERGING AND IF IT BECAME NECESSARY TO GO AROUND TO AVOID TFC, TO OFFSET TO THE N AWAY FROM THE TFC. AT SOMEWHERE AROUND 500 FT THE TFC WAS IN MY OPINION TOO CLOSE TO CONTINUE THE APCH. TCASII GAVE A TFC ALERT AT THE SAME TIME AND WE EXECUTED A GAR. RETURN TO THE ARPT WAS NORMAL WITH ABOUT A 10 MIN DELAY. AFTER LNDG THE TWR QUERIED US AS TO THE REASON FOR THE GAR. I REPLIED 'INADEQUATE SEPARATION, TCASII ALERT AND 2 AIRPLANES OCCUPYING THE SAME AIRSPACE AT THE SAME TIME.' THE TWR ASKED US TO CALL AFTER PARKING. WHEN I TALKED TO THE TWR CAB, THEY WANTED TO KNOW THE REASON FOR THE GAR, AS I CITED INADEQUATE SEPARATION. I REPLIED IT MAY HAVE BEEN WITHIN THEIR REQUIREMENTS, BUT I FELT IT WAS TOO CLOSE FOR US AND WE ELECTED TO GO AROUND. HE ASKED IF WE HAD THE OTHER TFC IN SIGHT WHEN ADVISED. I SAID WE DID, BUT AS THE TFC CONVERGED, IT DIDN'T LOOK SAFE TO CONTINUE, SO WE WENT AROUND. THE TWR ASKED IF WE HAD DONE THIS TYPE OF APCH BEFORE. I STATED I HAD AND HAVE EVEN BEEN THE ACFT ON THE S SIDE TO RWY 10. THE TWR IMPLIED THEY WERE HAPPY WITH THE ANSWERS. MY SAFETY CONCERNS WITH THESE APCHS ARE AS FOLLOWS: AT SJU, THE BRIDGE VISUAL TO RWY 10 AND THE LAGOON VISUAL TO RWY 8 ARE CONVERGING APCHS REQUIRING LOW ALT MANEUVERING BELOW 500 FT. ACFT APCHING FROM THE S ON THE BRIDGE VISUAL ARE REQUIRED TO MAKE A 90 DEG R TURN TO FINAL WHILE ACFT ON THE LAGOON VISUAL ARE REQUIRED TO MAKE A L TURN ABOUT 20 DEGS. FINAL APCH COURSES OF THESE 2 RWY INTERSECT APPROX 3000 FT FROM THE APCH END OF THE RWYS. THE POSSIBILITY OF AN ACFT TURNING TO RWY 10 OVERSHOOTING FINAL IS HIGH. THE MANEUVERING ALSO PUTS BOTH ACFT BELLY TO BELLY IN SUCH A POS THAT PLTS WILL LOSE VISUAL CONTACT WITH THE OTHER AT LOW ALT. I RECOMMEND THAT SEPARATION BE GIVEN TO ACFT TO ENSURE THAT APCHS ARE STAGGERED ENOUGH TO ENSURE AN OVERSHOOT IS NOT CATASTROPHIC. SUPPLEMENTAL INFO FROM ACN 634216: THIS PRESENTED ITSELF VISUALLY BY CONSTANT BEARING AND DECREASING RANGE TO TFC (A TURBOPROP). SEVERAL PAX THANKED US AFTER LNDG FOR MOVING AWAY FROM TFC THAT APPEARED TO BE VERY CLOSE IN THEIR ESTIMATION.
Data retrieved from NASA's ASRS site as of July 2007 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.