37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 563474 |
Time | |
Date | 200210 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bos.airport |
State Reference | MA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B757 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : bos.tower |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : cfi pilot : multi engine pilot : instrument pilot : commercial pilot : flight engineer |
Experience | flight time last 90 days : 540 flight time total : 12000 flight time type : 2700 |
ASRS Report | 563474 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | incursion : runway non adherence : clearance other anomaly other |
Independent Detector | other controllera |
Resolutory Action | controller : issued alert |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Landed on runway 22L, holding short of runway 22R. Told to monitor tower. Departure control was bleeding over badly onto frequency plus occasional ATIS bleed-over. We mentioned this to tower and were informed of previous complaints. Told to expect at least a 2 min delay. With captain's concurrence, I went on PA to inform passenger and keep them seated. As I returned to communication #1, we were crossing runway 22R. After crossing, we were informed the clearance had been for company flight #abd, not us (flight #abc). We had no idea flight #abd was on frequency, as they had been told to monitor only. Factors: 1)frequency congestion and bleed-over. 2) similar call signs. 3) one pilot off frequency. Suggestions: 1) fix transmitter problem at bos. 2) both pilots stay on frequency at congested airports. 3) avoid common practice of similar call signs for same city.; 4) when able, controller should repeat call sign in critical sits when dealing with similar ones.
Original NASA ASRS Text
Title: A B757 FLT CREW, AFTER LNDG AT BOS, CROSSED THE PARALLEL, RESPONDING TO A CLRNC FOR ANOTHER ACFT WITH A SIMILAR CALL SIGN.
Narrative: LANDED ON RWY 22L, HOLDING SHORT OF RWY 22R. TOLD TO MONITOR TWR. DEP CTL WAS BLEEDING OVER BADLY ONTO FREQ PLUS OCCASIONAL ATIS BLEED-OVER. WE MENTIONED THIS TO TWR AND WERE INFORMED OF PREVIOUS COMPLAINTS. TOLD TO EXPECT AT LEAST A 2 MIN DELAY. WITH CAPT'S CONCURRENCE, I WENT ON PA TO INFORM PAX AND KEEP THEM SEATED. AS I RETURNED TO COM #1, WE WERE XING RWY 22R. AFTER XING, WE WERE INFORMED THE CLRNC HAD BEEN FOR COMPANY FLT #ABD, NOT US (FLT #ABC). WE HAD NO IDEA FLT #ABD WAS ON FREQ, AS THEY HAD BEEN TOLD TO MONITOR ONLY. FACTORS: 1)FREQ CONGESTION AND BLEED-OVER. 2) SIMILAR CALL SIGNS. 3) ONE PLT OFF FREQ. SUGGESTIONS: 1) FIX XMITTER PROB AT BOS. 2) BOTH PLTS STAY ON FREQ AT CONGESTED ARPTS. 3) AVOID COMMON PRACTICE OF SIMILAR CALL SIGNS FOR SAME CITY.; 4) WHEN ABLE, CTLR SHOULD REPEAT CALL SIGN IN CRITICAL SITS WHEN DEALING WITH SIMILAR ONES.
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.