37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1316167 |
Time | |
Date | 201512 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | DCA.Airport |
State Reference | DC |
Environment | |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi Initial Climb Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
We were operating [flight abcd]. I had obtained my clearance via the ACARS pre departure clearance; which gave us the squawk code and flight number and assigned route. I contacted ground using the correct call sign and ground responded with the incorrect call sign; but I did not think anything of it because it was a quick taxi and we were switched over to tower. We had to run the runway SID change checklist. Tower asked us if we were ready and we responded with that we needed a few minutes to run a checklist. I remember being confused because tower was calling us by the wrong flight number. After running the checklist we contacted tower and told them we were ready. The controller used the wrong flight number again and we attempted to correct him with emphasis on our flight number. I did mention this to the captain and he told the controller very plainly that we were [flight abcd]. Then the controller messed up the call sign again and cleared us for takeoff. Once we were airborne departure control told us that [flight abcd] was not an active flight and all they had on file was a [flight abdd]. ATC instructed us to change our call signs and squawk code. ATC was expecting us to use the flight plan for [abdd]; but we did not have that information because we had [abcd] clearance.due to this confusion we should have corrected the call sign before takeoff.
Original NASA ASRS Text
Title: There was confusion over a flight number at DCA. ATC was using one flight number and the crew had a different; similar flight number; but did not clarify ATC's mistake until after takeoff.
Narrative: We were operating [Flight ABCD]. I had obtained my clearance via the ACARS PDC; which gave us the squawk code and flight number and assigned route. I contacted ground using the correct call sign and ground responded with the incorrect call sign; but I did not think anything of it because it was a quick taxi and we were switched over to tower. We had to run the Runway SID change checklist. Tower asked us if we were ready and we responded with that we needed a few minutes to run a checklist. I remember being confused because tower was calling us by the wrong flight number. After running the checklist we contacted tower and told them we were ready. The controller used the wrong flight number again and we attempted to correct him with emphasis on our flight number. I did mention this to the Captain and he told the controller very plainly that we were [Flight ABCD]. Then the controller messed up the call sign again and cleared us for takeoff. Once we were airborne Departure Control told us that [Flight ABCD] was not an active flight and all they had on file was a [Flight ABDD]. ATC instructed us to change our call signs and squawk code. ATC was expecting us to use the flight plan for [ABDD]; but we did not have that information because we had [ABCD] clearance.Due to this confusion we should have corrected the call sign before takeoff.
Data retrieved from NASA's ASRS site 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.