 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air taxi pilot reported receiving a vector clearance to a fix on the filed flight plan when ATC meant for the vector to be to a similar-sounding fix on the SID.
| Attributes | |
| ACN | 1605878 |
| Time | |
| Date | 201812 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | RDU.Airport |
| State Reference | NC |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | SID ROZBO3 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Captain |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Part 91 flight [from] rdu. After the handoff from the tower my copilot contacted the departure control and after a couple of vectors the controller instructed to proceed to 'aigar' then my sic read back 'aigar' and we agreed to proceed to igary which was a fix on the fpl. Then the controller gave us the hand off to the next sector. After a few minutes the next controller asked us to which fix we were proceeding and we reported to igary as previously instructed; then he asked which SID we were flying and I reported ROZBO3. ATC probably realized we were going to a fix that was farther than they expected; even if on the same bearing and route; and gave us a clearance to proceed to chs; then igary; then flight plan route. The controller didn't mention any problem and didn't pass a phone number but as professional pilots we discussed this matter and we agreed that most probably the previous controller pronounced in the wrong way an intersection that was on the SID; specifically eager; that should be pronounced 'igar' and not 'aigr'. This was a particular case with two intersections on the same route; bearing and similar phonetics leaded to a misunderstanding. I think that in this case ATC should spell the name of the fix before giving a quick hand off; just to make sure the aircraft is proceeding to the assigned fix.
Original NASA ASRS Text
Title: Air taxi pilot reported receiving a vector clearance to a fix on the filed flight plan when ATC meant for the vector to be to a similar-sounding fix on the SID.
Narrative: Part 91 flight [from] RDU. After the handoff from the Tower my copilot contacted the Departure Control and after a couple of vectors the controller instructed to proceed to 'AIGAR' Then my SIC read back 'AIGAR' and we agreed to proceed to IGARY which was a fix on the FPL. Then the controller gave us the hand off to the next sector. After a few minutes the next controller asked us to which fix we were proceeding and we reported to IGARY as previously instructed; then he asked which SID we were flying and I reported ROZBO3. ATC probably realized we were going to a fix that was farther than they expected; even if on the same bearing and route; and gave us a clearance to proceed to CHS; then IGARY; then flight plan route. The controller didn't mention any problem and didn't pass a phone number but as professional pilots we discussed this matter and we agreed that most probably the previous controller pronounced in the wrong way an intersection that was on the SID; specifically EAGER; that should be pronounced 'IGAR' and not 'AIGR'. This was a particular case with two intersections on the same route; bearing and similar phonetics leaded to a misunderstanding. I think that in this case ATC should spell the name of the fix before giving a quick hand off; just to make sure the aircraft is proceeding to the assigned fix.
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.