 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
CL65 with ZMA described confused routing event allegedly resulting from ATC mispronouncing and/or misidentifying an intersection; along with the location of same.
| Attributes | |
| ACN | 823788 |
| Time | |
| Date | 200902 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZMA.ARTCC |
| State Reference | FL |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Regional Jet CL65 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 50 Flight Crew Total 5300 Flight Crew Type 1100 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
We were in cruise about 1 hour out of our destination of mbpv. ATC (ZMA) assigned direct solei. A while later; the controller asked us to confirm we were direct solei; we told him we were. A few minutes after that; ATC said we were south of a direct line to solei and we needed to turn 15 degrees left; so we did. I was then concerned about the integrity of our navigation equipment; so asked the controller to verify that the latitude/long for solei (which was the same on our chart and in our FMS) was correct. I read the latitude/long I showed for solei to the controller. His response was that was incorrect. The controller then read what he showed as the latitude/long for solei. We plugged the latitude/long that the controller gave us and navigated toward it. We were then handed off to mbpv approach who said after orede intersection proceed to xxxxx. We told the controller we came in over solei; to which he responded with 'direct' to a different fix. A few minutes later; the mbpv controller came on and said he talked to ZMA and they had sent us in over orede not solei. Now the mess-up was clear to us. ZMA had been saying solei when they meant to communicate orede to us. We looked at the latitude/long for orede and it matched exactly the latitude/long that ZMA had given us as the coordinates for solei.
Original NASA ASRS Text
Title: CL65 with ZMA described confused routing event allegedly resulting from ATC mispronouncing and/or misidentifying an intersection; along with the location of same.
Narrative: We were in cruise about 1 hour out of our destination of MBPV. ATC (ZMA) assigned direct SOLEI. A while later; the Controller asked us to confirm we were direct SOLEI; we told him we were. A few minutes after that; ATC said we were south of a direct line to SOLEI and we needed to turn 15 degrees left; so we did. I was then concerned about the integrity of our navigation equipment; so asked the Controller to verify that the LAT/LONG for SOLEI (which was the same on our chart and in our FMS) was correct. I read the LAT/LONG I showed for SOLEI to the Controller. His response was that was incorrect. The Controller then read what he showed as the LAT/LONG for SOLEI. We plugged the LAT/LONG that the Controller gave us and navigated toward it. We were then handed off to MBPV Approach who said after OREDE Intersection proceed to XXXXX. We told the Controller we came in over SOLEI; to which he responded with 'direct' to a different fix. A few minutes later; the MBPV Controller came on and said he talked to ZMA and they had sent us in over OREDE not SOLEI. Now the mess-up was clear to us. ZMA had been saying SOLEI when they meant to communicate OREDE to us. We looked at the LAT/LONG for OREDE and it matched exactly the LAT/LONG that ZMA had given us as the coordinates for SOLEI.
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.