37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 319165 |
Time | |
Date | 199510 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : phx |
State Reference | AZ |
Altitude | msl bound lower : 1500 msl bound upper : 1500 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : phx tower : phx |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 135 |
Flight Phase | climbout : initial climbout : takeoff |
Route In Use | approach : visual departure other departure sid : sid |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 135 |
Flight Phase | climbout : initial climbout : takeoff |
Route In Use | departure other departure sid : sid enroute other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 220 flight time total : 2800 flight time type : 1250 |
ASRS Report | 319165 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : airborne less severe non adherence : clearance non adherence : published procedure non adherence : required legal separation other anomaly other other spatial deviation |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew faa : investigated |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On oct/xx/95, flight abc was involved in a radio mishap. I was the first officer and the PF. Captain was the PNF. I accepted position and hold while company flight abd was cleared takeoff. Soon after I took a clearance which was to maintain a visual on company and cleared for takeoff runway 8L. I repeated myself to the controller. After takeoff I kept company in sight while on the drake 6 departure. Captain resumed the position as the PNF and took charge of the radios, which is policy. Captain changed to departure frequency and checked on and proceeded to tell me to turn left which was prior to the drake 6 turn. I then questioned the early turn and was ordered to turn anyway because he felt it was an oversight on tower's part. Other xmissions took place between captain and the controller. It was during one of these xmissions that I realized that captain had been responding with the wrong call sign. We were flight abc not flight abd. Flight abd had taken off shortly before us. To make captain aware of his error I pointed to our call sign which I had posted to the avionics panel prior to flight. It was during this time that departure gave us a number to call, at our earliest convenience. When captain asked the controller what it was in regards to, the controller said he did not know. After captain spoke to a controller, it was my understanding that air carrier Z was taking off from runway 8R and tower was trying to talk to us while we were on departure frequency, therefore resulting in a separation problem for the tower. I have always made it one of my priorities to attach the manifest in a clearly printed bold lettering for each flight to the avionics panel for both my captain and myself to refer to and will continue to do so. As an additional preventive measure I will now verbally reiterate to my captain the flight number to verify its accuracy and will continue to refer to the flight number while in flight. Example: 'captain the passenger count for this flight is booked to 16.' now I will say 'captain the passenger count for flight abc is booked to 16.' I now see the importance of monitoring other xmissions on common communication frequency and will question any abnormalities, such as a third party between me and the controller, in hope of preventing this to happen to any other flts.
Original NASA ASRS Text
Title: FREQ CHANGE PREMATURE CREATED BY REPLY TO WRONG CALL SIGN. SETS UP A POTENTIAL CONFLICT WITH 2 DEP ACFT.
Narrative: ON OCT/XX/95, FLT ABC WAS INVOLVED IN A RADIO MISHAP. I WAS THE FO AND THE PF. CAPT WAS THE PNF. I ACCEPTED POS AND HOLD WHILE COMPANY FLT ABD WAS CLRED TKOF. SOON AFTER I TOOK A CLRNC WHICH WAS TO MAINTAIN A VISUAL ON COMPANY AND CLRED FOR TKOF RWY 8L. I REPEATED MYSELF TO THE CTLR. AFTER TKOF I KEPT COMPANY IN SIGHT WHILE ON THE DRAKE 6 DEP. CAPT RESUMED THE POS AS THE PNF AND TOOK CHARGE OF THE RADIOS, WHICH IS POLICY. CAPT CHANGED TO DEP FREQ AND CHKED ON AND PROCEEDED TO TELL ME TO TURN L WHICH WAS PRIOR TO THE DRAKE 6 TURN. I THEN QUESTIONED THE EARLY TURN AND WAS ORDERED TO TURN ANYWAY BECAUSE HE FELT IT WAS AN OVERSIGHT ON TWR'S PART. OTHER XMISSIONS TOOK PLACE BTWN CAPT AND THE CTLR. IT WAS DURING ONE OF THESE XMISSIONS THAT I REALIZED THAT CAPT HAD BEEN RESPONDING WITH THE WRONG CALL SIGN. WE WERE FLT ABC NOT FLT ABD. FLT ABD HAD TAKEN OFF SHORTLY BEFORE US. TO MAKE CAPT AWARE OF HIS ERROR I POINTED TO OUR CALL SIGN WHICH I HAD POSTED TO THE AVIONICS PANEL PRIOR TO FLT. IT WAS DURING THIS TIME THAT DEP GAVE US A NUMBER TO CALL, AT OUR EARLIEST CONVENIENCE. WHEN CAPT ASKED THE CTLR WHAT IT WAS IN REGARDS TO, THE CTLR SAID HE DID NOT KNOW. AFTER CAPT SPOKE TO A CTLR, IT WAS MY UNDERSTANDING THAT ACR Z WAS TAKING OFF FROM RWY 8R AND TWR WAS TRYING TO TALK TO US WHILE WE WERE ON DEP FREQ, THEREFORE RESULTING IN A SEPARATION PROB FOR THE TWR. I HAVE ALWAYS MADE IT ONE OF MY PRIORITIES TO ATTACH THE MANIFEST IN A CLRLY PRINTED BOLD LETTERING FOR EACH FLT TO THE AVIONICS PANEL FOR BOTH MY CAPT AND MYSELF TO REFER TO AND WILL CONTINUE TO DO SO. AS AN ADDITIONAL PREVENTIVE MEASURE I WILL NOW VERBALLY REITERATE TO MY CAPT THE FLT NUMBER TO VERIFY ITS ACCURACY AND WILL CONTINUE TO REFER TO THE FLT NUMBER WHILE IN FLT. EXAMPLE: 'CAPT THE PAX COUNT FOR THIS FLT IS BOOKED TO 16.' NOW I WILL SAY 'CAPT THE PAX COUNT FOR FLT ABC IS BOOKED TO 16.' I NOW SEE THE IMPORTANCE OF MONITORING OTHER XMISSIONS ON COMMON COM FREQ AND WILL QUESTION ANY ABNORMALITIES, SUCH AS A THIRD PARTY BTWN ME AND THE CTLR, IN HOPE OF PREVENTING THIS TO HAPPEN TO ANY OTHER FLTS.
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.