 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 first officer reported a heading deviation due to confusion and communication breakdown with ATC.
| Attributes | |
| ACN | 1558037 |
| Time | |
| Date | 201807 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | PHX.Airport |
| State Reference | AZ |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | Visual Approach STAR EAGUL 6 |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 689 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Crew was approaching the sky harbor airport on the eagul 6 arrival. Just passing dervl descending though approximately 5300 ft.; approach control gave the crew position of the field and inquired whether we had the airfield visually. We told the approach controller that we had the field in sight and he cleared us for the visual for runway 26. Although the clearance did not include a heading to join the final approach course; both crew members agreed that we were; in fact; cleared the visual approach. The pilot switched the automation to heading mode and turned to a heading of 230 to join the final approach course to runway 26.the controller then asked where we were headed; and we told him that we were on a heading to fly the visual to 26. He then said that we were not cleared the visual and gave a more southerly heading to intercept the final approach course and to maintain 5000 ft. We leveled off at 5000 ft. And complied with the new clearance. The flight concluded uneventfully with a landing on runway 26 and taxi to the gate.the controller's phraseology was confusing. Both crew members were in agreement that the clearance was given to fly the visual to runway 26. Although the phraseology seemed a bit inconsistent with phoenix controllers; the flight crew should have confirmed the clearance.
Original NASA ASRS Text
Title: B737 First Officer reported a heading deviation due to confusion and communication breakdown with ATC.
Narrative: Crew was approaching the Sky Harbor Airport on the EAGUL 6 Arrival. Just passing DERVL descending though approximately 5300 ft.; Approach Control gave the crew position of the field and inquired whether we had the airfield visually. We told the Approach Controller that we had the field in sight and he cleared us for the visual for Runway 26. Although the clearance did not include a heading to join the final approach course; both crew members agreed that we were; in fact; cleared the visual approach. The Pilot switched the automation to Heading mode and turned to a heading of 230 to join the final approach course to Runway 26.The Controller then asked where we were headed; and we told him that we were on a heading to fly the visual to 26. He then said that we were not cleared the visual and gave a more southerly heading to intercept the final approach course and to maintain 5000 ft. We leveled off at 5000 ft. and complied with the new clearance. The flight concluded uneventfully with a landing on Runway 26 and taxi to the gate.The Controller's phraseology was confusing. Both crew members were in agreement that the clearance was given to fly the visual to Runway 26. Although the phraseology seemed a bit inconsistent with Phoenix Controllers; the flight crew should have confirmed the clearance.
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.