37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1125498 |
Time | |
Date | 201310 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | JFK.Airport |
State Reference | NY |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | B747 Undifferentiated or Other Model |
Operating Under FAR Part | Part 129 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
[Jfk was] departing 22R landing 22L/right and departing 31L at ke. I departed an air carrier and cleared a B757 to luaw [runway] 22R; I also began to give the B757 traffic for an arrival to [runway] 22R; and then made the determination that this traffic was still being vectored for the approach and was no factor. I departed another air carrier from [runway] 31L at ke; and made a rolling call for [the runway 31L departure] and the B757. I cleared the B757 for takeoff and began coordinate with local control 1 to cross [runway] 22R. Local control 1 was giving taxing instructions to another aircraft; I observed local control 1's etvs to see when the readback stopped. I said 'behind the B757 rolling now; cross [runway] 1 at 'G' and [runway] 1 at 'H'. A B747 was at 'G' and another B747 was at 'H'. Local control 1 was receiving a call from the approach controller at this time; there was no way for me to be aware that he was currently involved in separate coordination; and never read back the exact instructions. Local control 1 heard '....now cross [runway] 1 at 'G' and [runway] 1 at 'H'. I heard local control 1 instruct someone to 'turn left on 'a'. I didn't realize this was the end of the clearance which would have included crossing instructions to [the B747 at G] but rather I thought he was speaking to the ground controller. I heard him began to talk to the second B747 at 'H'; and then realized what was happening; shouted to local control 1 to 'no; no! I'm rolling!' and then cancelled take off clearance for the B757. The B757 acknowledged and began to stop. [The B747 at G] and [the B747 at H] never began to move. The B757 taxied off the runway and returned to the ramp. The use of standardized phraseology to initiate crossings and the use of standard phraseology to confirm the proper instructions would have prevented this. We do this operation frequently to great effectiveness; but we do not have exact phraseology or methodology prescribed in our SOP to do this. As an example; some controllers may begin coordination prior to issuing takeoff clearance; while others (such as myself) do so after. The 7110 procedure; from my understanding; is based on coordination between ground control and local control. We use this standardized procedure as a framework for our specific operations. After conversing with the other controller involved; we came to the determination that my use of the word 'now' (to indicate the B757 is now rolling) and him not reading back my instructions; (he was involved in coordination with the approach controller via the etvs) are what contributed to this event.
Original NASA ASRS Text
Title: JFK Controller described a developing ground conflict event when the coordination between the two local controllers was confused with regard to runway crossings; the reporter suggests phraseology standardization.
Narrative: [JFK was] departing 22R landing 22L/R and departing 31L at KE. I departed an Air Carrier and cleared a B757 to LUAW [Runway] 22R; I also began to give the B757 traffic for an arrival to [Runway] 22R; and then made the determination that this traffic was still being vectored for the approach and was no factor. I departed another Air Carrier from [Runway] 31L at KE; and made a rolling call for [the Runway 31L departure] and the B757. I cleared the B757 for takeoff and began coordinate with Local Control 1 to cross [Runway] 22R. Local Control 1 was giving taxing instructions to another aircraft; I observed Local Control 1's ETVS to see when the readback stopped. I said 'Behind the B757 rolling now; cross [Runway] 1 at 'G' and [Runway] 1 at 'H'. A B747 was at 'G' and another B747 was at 'H'. Local Control 1 was receiving a call from the Approach Controller at this time; there was no way for me to be aware that he was currently involved in separate coordination; and never read back the exact instructions. Local Control 1 heard '....now cross [Runway] 1 at 'G' and [Runway] 1 at 'H'. I heard Local Control 1 instruct someone to 'turn left on 'A'. I didn't realize this was the end of the clearance which would have included crossing instructions to [the B747 at G] but rather I thought he was speaking to the Ground Controller. I heard him began to talk to the second B747 at 'H'; and then realized what was happening; shouted to Local Control 1 to 'No; no! I'm rolling!' and then cancelled take off clearance for the B757. The B757 acknowledged and began to stop. [The B747 at G] and [the B747 at H] never began to move. The B757 taxied off the runway and returned to the ramp. The use of standardized phraseology to initiate crossings and the use of standard phraseology to confirm the proper instructions would have prevented this. We do this operation frequently to great effectiveness; but we do not have exact phraseology or methodology prescribed in our SOP to do this. As an example; some controllers may begin coordination prior to issuing takeoff clearance; while others (such as myself) do so after. The 7110 procedure; from my understanding; is based on coordination between Ground Control and Local Control. We use this standardized procedure as a framework for our specific operations. After conversing with the other Controller involved; we came to the determination that my use of the word 'now' (to indicate the B757 is now rolling) and him not reading back my instructions; (he was involved in coordination with the Approach Controller via the ETVS) are what contributed to this event.
Data retrieved from NASA's ASRS site as of July 2013 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.