37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 516640 |
Time | |
Date | 200107 |
Day | Sun |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : phl.airport |
State Reference | PA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : phl.tower |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | other personnel |
ASRS Report | 516640 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : published procedure non adherence : company policies other anomaly other |
Independent Detector | other other : disp1 |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Company |
Primary Problem | Company |
Narrative:
Flight abc air carrier X (den-phl) was on the ground in phl the same time flight abc air carrier X (phl-bdl) was taxiing out for takeoff. ATC delays due to WX caused flight abc air carrier X (den-phl) to be over 1 hour late arriving phl. I started my shift at XA00 and within the first min on duty, I received a message of a flight number overlap. I then checked both flts and found that flight abc air carrier X (den-phl) was taxiing to the gate the same time flight abc air carrier X (phl-btv) was taxiing to take off. I sent a message to both flts warning them of the situation, and ti told them to verify their call sign when talking to ATC. I tried calling our ramp control in phl, but received a busy signal 4 times. At XA06, flight abc air carrier X (den-phl) terminated at the gate. At XA10 flight abc air carrier X was airborne. Had the computers caught this overlap earlier, the flts could have been stubbed to have different flight numbers.
Original NASA ASRS Text
Title: 2 ACFT WITH THE SAME FLT NUMBER WERE ON THE GND AT PHL AT THE SAME TIME, ONE ARRIVING, THE OTHER DEPARTING.
Narrative: FLT ABC ACR X (DEN-PHL) WAS ON THE GND IN PHL THE SAME TIME FLT ABC ACR X (PHL-BDL) WAS TAXIING OUT FOR TKOF. ATC DELAYS DUE TO WX CAUSED FLT ABC ACR X (DEN-PHL) TO BE OVER 1 HR LATE ARRIVING PHL. I STARTED MY SHIFT AT XA00 AND WITHIN THE FIRST MIN ON DUTY, I RECEIVED A MESSAGE OF A FLT NUMBER OVERLAP. I THEN CHKED BOTH FLTS AND FOUND THAT FLT ABC ACR X (DEN-PHL) WAS TAXIING TO THE GATE THE SAME TIME FLT ABC ACR X (PHL-BTV) WAS TAXIING TO TAKE OFF. I SENT A MESSAGE TO BOTH FLTS WARNING THEM OF THE SIT, AND TI TOLD THEM TO VERIFY THEIR CALL SIGN WHEN TALKING TO ATC. I TRIED CALLING OUR RAMP CTL IN PHL, BUT RECEIVED A BUSY SIGNAL 4 TIMES. AT XA06, FLT ABC ACR X (DEN-PHL) TERMINATED AT THE GATE. AT XA10 FLT ABC ACR X WAS AIRBORNE. HAD THE COMPUTERS CAUGHT THIS OVERLAP EARLIER, THE FLTS COULD HAVE BEEN STUBBED TO HAVE DIFFERENT FLT NUMBERS.
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.