37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 815476 |
Time | |
Date | 200812 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : tus.vortac |
State Reference | AZ |
Altitude | msl single value : 4500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : tus.tracon |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level |
Flight Plan | None |
Aircraft 2 | |
Controlling Facilities | tracon : tus.tracon |
Operator | general aviation : corporate |
Make Model Name | PC-12 |
Flight Phase | descent : vacating altitude |
Flight Plan | VFR |
Person 1 | |
Function | flight crew : single pilot |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 71 flight time total : 10290 flight time type : 600 |
ASRS Report | 815476 |
Events | |
Anomaly | conflict : nmac |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action |
Miss Distance | horizontal : 100 vertical : 100 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Narrative:
The approach controller issued a TA for traffic at 2 o'clock and 2 miles. We could not make visual contact with the traffic and shortly thereafter the controller advised us that 'if traffic not in-sight turn 30 degrees left immediately.' we turned left and immediately saw the other aircraft descending upon us from the 10 o'clock direction. We immediately took evasive action and avoided the aircraft. Tucson TRACON does a lot of training for new controllers and I feel that this was a contributory factor. New controllers can sometimes misinterpret positions and/or instructions that need to be transmitted to pilots in the air. At the time of event the airspace around tucson was very busy and this probably contributed also (high workload).
Original NASA ASRS Text
Title: Enroute VFR C172 at 4500 with TUS Approach Controller experienced NMAC when Controller's traffic call clock position and turn instructions were based upon the wrong location of the conflicting traffic.
Narrative: The Approach Controller issued a TA for traffic at 2 o'clock and 2 miles. We could not make visual contact with the traffic and shortly thereafter the Controller advised us that 'if traffic not in-sight turn 30 degrees left immediately.' We turned left and immediately saw the other aircraft descending upon us from the 10 o'clock direction. We immediately took evasive action and avoided the aircraft. Tucson TRACON does a lot of training for new Controllers and I feel that this was a contributory factor. New Controllers can sometimes misinterpret positions and/or instructions that need to be transmitted to Pilots in the air. At the time of event the airspace around Tucson was very busy and this probably contributed also (high workload).
Data retrieved from NASA's ASRS site as of May 2009 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.