37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1016055 |
Time | |
Date | 201206 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | JFK.Airport |
State Reference | NY |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 230 Flight Crew Total 8027 Flight Crew Type 3000 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance |
Narrative:
An A320 was in position on runway 4L; a B757 was in position on runway 31L ke intersection. I issued the B757 takeoff clearance; the A320 took the B757 clearance and did read it back with his call sign. The B757 immediately asked for a confirmation of the take off clearance. I then restated the B757's clearance to take off. He then stated that he someone else took his take off clearance. At this point I noticed the A320 had begun his departure roll on runway 4L. He may have gone a hundred feet down the runway when he stopped and asked if he was cleared for take off. I stated that I did not clear him for take off but he was at this time now cleared for take off. There was no loss of separation or possibility of it. The A320 and the B757 both departed with no further issues. Pilots and controllers must be more aware of hear back read back errors. I did not realize that the A320 read back the B757 clearance. I heard what I thought was the B757 acknowledging the clearance. The call signs were similar but not similar enough that I pointed them out to both pilots. The A320 heard what he was waiting to hear even though the clearance was not for him.
Original NASA ASRS Text
Title: JFK Controller described a confused take off event when an Air Carrier initiated a take off without being cleared; confused by another another Air Carrier's clearance departing an intersecting runway.
Narrative: An A320 was in position on Runway 4L; a B757 was in position on Runway 31L KE Intersection. I issued the B757 takeoff clearance; the A320 took the B757 clearance and did read it back with his call sign. The B757 immediately asked for a confirmation of the take off clearance. I then restated the B757's clearance to take off. He then stated that he someone else took his take off clearance. At this point I noticed the A320 had begun his departure roll on Runway 4L. He may have gone a hundred feet down the runway when he stopped and asked if he was cleared for take off. I stated that I did not clear him for take off but he was at this time now cleared for take off. There was no loss of separation or possibility of it. The A320 and the B757 both departed with no further issues. Pilots and controllers must be more aware of hear back read back errors. I did not realize that the A320 read back the B757 clearance. I heard what I thought was the B757 acknowledging the clearance. The call signs were similar but not similar enough that I pointed them out to both pilots. The A320 heard what he was waiting to hear even though the clearance was not for him.
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.