 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A300 first officer reports difficulty understanding ATC during arkes RNAV departure from fll and proceeds toward the wrong fix.
| Attributes | |
| ACN | 921583 |
| Time | |
| Date | 201011 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | FLL.Airport |
| State Reference | FL |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | A300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Route In Use | SID ARKES |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Experience | Air Traffic Control Military 15 Air Traffic Control Radar 20 Flight Crew Last 90 Days 50 Flight Crew Total 5000 Flight Crew Type 1400 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
We were assigned the arkes RNAV SID per our pre departure clearance. The SID was loaded into the FMS and briefed. Tower assigned us a heading and cleared us for takeoff. After takeoff we switched to departure and checked in with our heading and altitude. Departure cleared us direct to a fix. We were unsure of what the controller said and asked for him to repeat the clearance. After he responded the captain and I both looked at out SID chart and determined that we were cleared to hapor on the arkes SID. Hapor was the next point on the SID. After we turned towards hapor the controller told us to turn to 320 and asked if we were heading to arkes? We again could not make out what he was saying and asked him to repeat the fix name. He responded with 'were you not assigned the arkes SID for departure?' we replied yes; and knew immediately that he had been saying arkes all along. We apologized for our misunderstanding and turned direct to arkes. He then cleared us to a higher altitude and switched us to center. There was no mention of any problems or traffic conflicts. We showed no other traffic on our TCAS at the time.after we had completed our climb we discussed our error and determined that it was caused by a combination of the following factors:- we were unfamiliar with the SID and although we briefed the departure we were not familiar with the pronunciation of the fix names.- communications were garbled and hard to hear at that time. This was due to our low altitude; high ambient cockpit noise; and weak reception of the controller.- expectation bias. We anticipated flying the SID as published. As a result; we heard what we were expecting; hapor; which was the next point on the SID.- finally the arkes fix; as depicted on our chart is in such a position that when both pilots had it clipped to the yoke chart holder; arkes was covered by the chart clip. This kept us from seeing the fix and possibly identifying it as what the controller was saying.
Original NASA ASRS Text
Title: A300 First Officer reports difficulty understanding ATC during ARKES RNAV departure from FLL and proceeds toward the wrong fix.
Narrative: We were assigned the ARKES RNAV SID per our PDC. The SID was loaded into the FMS and Briefed. Tower assigned us a heading and cleared us for takeoff. After takeoff we switched to Departure and checked in with our heading and altitude. Departure cleared us direct to a fix. We were unsure of what the Controller said and asked for him to repeat the clearance. After he responded the Captain and I both looked at out SID chart and determined that we were cleared to HAPOR on the ARKES SID. HAPOR was the next point on the SID. After we turned towards HAPOR the Controller told us to turn to 320 and asked if we were heading to ARKES? We again could not make out what he was saying and asked him to repeat the fix name. He responded with 'were you not assigned the ARKES SID for departure?' We replied yes; and knew immediately that he had been saying ARKES all along. We apologized for our misunderstanding and turned direct to ARKES. He then cleared us to a higher altitude and switched us to Center. There was no mention of any problems or traffic conflicts. We showed no other traffic on our TCAS at the time.After we had completed our climb we discussed our error and determined that it was caused by a combination of the following factors:- We were unfamiliar with the SID and although we briefed the departure we were not familiar with the pronunciation of the fix names.- Communications were garbled and hard to hear at that time. This was due to our low altitude; high ambient cockpit noise; and weak reception of the Controller.- Expectation bias. We anticipated flying the SID as published. As a result; we heard what we were expecting; HAPOR; which was the next point on the SID.- Finally the ARKES fix; as depicted on our chart is in such a position that when both pilots had it clipped to the yoke chart holder; ARKES was covered by the chart clip. This kept us from seeing the fix and possibly identifying it as what the Controller was saying.
Data retrieved from NASA's ASRS site as of April 2012 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.