 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Language barrier between VFR pilot and controller delayed an airborne conflict resolution with another VFR aircraft.
| Attributes | |
| ACN | 1151677 |
| Time | |
| Date | 201402 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZLC.ARTCC |
| State Reference | UT |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Cruise |
| Route In Use | VFR Route |
| Flight Plan | VFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Radar 14 Air Traffic Control Time Certified In Pos 1 (yrs) 11 |
| Events | |
| Anomaly | Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Cessna departed the airport and requested VFR flight following. Due to a language barrier; it was very difficult to understand the call sign. The airplane was eastbound at approximately 6;500 MSL. Looking ahead at traffic; and understanding the language barrier; I in plain language told the pilot the aircraft needed to be at appropriate VFR cruising altitudes. There was an opposite direction target at 6;400 MSL the exact altitude. I called traffic. The pilot acknowledged. As they continued to get closer and obviously merging; I again warned the pilot to climb. We then found the call sign was incorrect; but the pilot was answering the calls. At four miles; the targets looked very likely to merge I told the pilot to deviate right and maintain VFR. The aircraft did not turn. At two miles I again told the pilot to turn right; at a brief pause another pilot from the frequency said over the frequency 'turn right!' the pilot did and said thank you; the targets got very close.radios may have been an issue; however the d-side and I were both hearing different call signs. Language barrier was the biggest issue.
Original NASA ASRS Text
Title: Language barrier between VFR pilot and Controller delayed an airborne conflict resolution with another VFR aircraft.
Narrative: Cessna departed the airport and requested VFR flight following. Due to a language barrier; it was very difficult to understand the call sign. The airplane was eastbound at approximately 6;500 MSL. Looking ahead at traffic; and understanding the language barrier; I in plain language told the pilot the aircraft needed to be at appropriate VFR cruising altitudes. There was an opposite direction target at 6;400 MSL the exact altitude. I called traffic. The pilot acknowledged. As they continued to get closer and obviously merging; I again warned the pilot to climb. We then found the call sign was incorrect; but the pilot was answering the calls. At four miles; the targets looked very likely to merge I told the pilot to deviate right and maintain VFR. The aircraft did not turn. At two miles I again told the pilot to turn right; at a brief pause another pilot from the frequency said over the frequency 'turn right!' The pilot did and said thank you; the targets got very close.Radios may have been an issue; however the D-Side and I were both hearing different call signs. Language barrier was the biggest issue.
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.