37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 928877 |
Time | |
Date | 201101 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | NCT.TRACON |
State Reference | CA |
Aircraft 1 | |
Make Model Name | B757 Undifferentiated or Other Model |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Person 1 | |
Function | Departure |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Aircraft X; a B757; departing sfo runway 28 westbound. On the flight plan he had filed ksfo.CUIT2. Sac.J65.pmd but the preferential routing was +ksfo.PORTE3.wages..pmd+; shown on the flight progress strip. Aircraft X departed runway 28 and at about 2;200 ft appeared to start a right turn (which would have been correct to fly the cuit departure. I immediately turned him left heading 270 and I believe I said for traffic. He seemed confused and questioned the turn so was a little slow in reacting. In the meantime aircraft Y; an E120 departed runway 1L on a EUGEN5 departure. The CI1 (coordinator) called sfo tower to give them a 'heads up' on aircraft X and they gave aircraft Y a right turn to a 010 heading. The separation was about four miles at that point (three required since aircraft Y was not directly behind aircraft X) and increasing due to the headings assigned. I had to wait a little to turn aircraft Y back to the eugen departure to get the required five miles for an E120 behind a B757 as the departures come off different runways but eventually follow the same general route. I then explained to aircraft X that he should have been on the porte route which would have been a 280 heading off runway 28. He seemed concerned that maybe there would be a 'problem' to which I said; 'no we kept the required separation. I did explain that I saw he had filed the cuit but the preferential (porte) should have been flown. I then gave him vectors to pmd and figuring 'no harm; no foul' I went on working the session. Later the OM came to the area and said the aircraft Y pilot was on the phone concerned about the operation and the quick turn the tower had given from a 350 to a 010 heading right before the frequency change. He wondered if there was a separation problem. I told the OM I was sure that was not an issue. What may be an issue though is in this ACARS environment this is not the first time I have seen something like this. In the 'old days' clearance delivery could clarify and make sure proper routing's were issued when a filed route was so completely different from the pdr. What is the procedure for transmitting and ensuring the proper receipt of a clearance these days? The situation on first look didn't seem that bad but; had I not caught it right away and CI1 and the sfo local reacted as they did; it may have become a dangerous situation. There needs to be a way to ensure that a complete understanding of the route is received by the pilot.
Original NASA ASRS Text
Title: A near conflict occurred when traffic departing from Runway 28 and Runway 1 at SFO turned toward one another because the clearance issued to the Runway 28 traffic was confused and/or not updated.
Narrative: Aircraft X; a B757; departing SFO Runway 28 westbound. On the flight plan he had filed KSFO.CUIT2. SAC.J65.PMD but the preferential routing was +KSFO.PORTE3.WAGES..PMD+; shown on the flight progress strip. Aircraft X departed Runway 28 and at about 2;200 FT appeared to start a right turn (which would have been correct to fly the CUIT departure. I immediately turned him left heading 270 and I believe I said for traffic. He seemed confused and questioned the turn so was a little slow in reacting. In the meantime Aircraft Y; an E120 departed Runway 1L on a EUGEN5 departure. The CI1 (Coordinator) called SFO Tower to give them a 'heads up' on Aircraft X and they gave Aircraft Y a right turn to a 010 heading. The separation was about four miles at that point (three required since Aircraft Y was not directly behind Aircraft X) and increasing due to the headings assigned. I had to wait a little to turn Aircraft Y back to the EUGEN departure to get the required five miles for an E120 behind a B757 as the departures come off different runways but eventually follow the same general route. I then explained to Aircraft X that he should have been on the PORTE route which would have been a 280 heading off Runway 28. He seemed concerned that maybe there would be a 'problem' to which I said; 'No we kept the required separation. I did explain that I saw he had filed the CUIT but the preferential (PORTE) should have been flown. I then gave him vectors to PMD and figuring 'no harm; no foul' I went on working the session. Later the OM came to the area and said the Aircraft Y pilot was on the phone concerned about the operation and the quick turn the Tower had given from a 350 to a 010 heading right before the frequency change. He wondered if there was a separation problem. I told the OM I was sure that was not an issue. What may be an issue though is in this ACARS environment this is not the first time I have seen something like this. In the 'old days' Clearance Delivery could clarify and make sure proper routing's were issued when a filed route was so completely different from the PDR. What is the procedure for transmitting and ensuring the proper receipt of a clearance these days? The situation on first look didn't seem that bad but; had I not caught it right away and CI1 and the SFO Local reacted as they did; it may have become a dangerous situation. There needs to be a way to ensure that a complete understanding of the route is received by the pilot.
Data retrieved from NASA's ASRS site as of April 2012 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.