37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1267697 |
Time | |
Date | 201506 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | TEB.Tower |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Transport |
Operating Under FAR Part | Part 135 |
Flight Phase | Climb |
Route In Use | SID TEB9 |
Flight Plan | IFR |
Person 1 | |
Function | Ground |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 5.0 |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance |
Narrative:
A flight called ground control for taxi. A similar aircraft [same company with the same first and last digit in three digit flight number] also had a flight progress strip for a VFR departure. On ground control; I issued instructions that would be relevant for a VFR departure and used the full call sign flight 2. Flight 1 answered; read back the instructions; and used his call sign (flight 1). Flight 1 continued to the runway; where he was switched to local control; who issued a VFR climbout instruction and cleared him for takeoff. Flight 1 (still answering to flight 2's call sign; but reading back his own) departed; did not follow the instructions; and flew the teterboro 9 departure procedure. Departure control was notified and no loss of separation occurred. The readback/hearback error occurred initially on my position (ground control) however at no point did flight 1 make an attempt to correct the call sign. He also accepted a VFR departure clearance; then flew an IFR flight path without questioning the instructions. Pilots need to be more aware of the instructions they're issued and if they don't match their clearances; at the bare minimum question them before taking off.
Original NASA ASRS Text
Title: Turboprop flight crew with an IFR clearance accepts taxi and takeoff instructions for a company VFR flight with a very similar call sign. The First Officer read back his call sign each time thinking the Controller was making an error and the controller ignored it each time thinking the pilot was making an error.
Narrative: A flight called Ground Control for taxi. A similar aircraft [same company with the same first and last digit in three digit flight number] also had a flight progress strip for a VFR departure. On Ground Control; I issued instructions that would be relevant for a VFR departure and used the full call sign Flight 2. Flight 1 answered; read back the instructions; and used his call sign (Flight 1). Flight 1 continued to the runway; where he was switched to Local Control; who issued a VFR climbout instruction and cleared him for takeoff. Flight 1 (still answering to Flight 2's call sign; but reading back his own) departed; did not follow the instructions; and flew the Teterboro 9 Departure procedure. Departure Control was notified and no loss of separation occurred. The readback/hearback error occurred initially on my position (Ground Control) however at no point did Flight 1 make an attempt to correct the call sign. He also accepted a VFR departure clearance; then flew an IFR flight path without questioning the instructions. Pilots need to be more aware of the instructions they're issued and if they don't match their clearances; at the bare minimum question them before taking off.
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.