 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Helicopter X non adherence to ATC instructions had less than standard separation from air carrier Y. Pilot deviation. System error.
| Attributes | |
| ACN | 205712 |
| Time | |
| Date | 199203 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : zzz |
| State Reference | US |
| Altitude | msl bound lower : 1500 msl bound upper : 1500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : zzz tower : zzz |
| Operator | other |
| Make Model Name | Helicopter |
| Flight Phase | cruise other |
| Route In Use | approach : visual |
| Flight Plan | None |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Flight Phase | climbout : initial |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar |
| Experience | controller radar : 7 |
| ASRS Report | 205712 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : non radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation non adherence : clearance non adherence : published procedure other spatial deviation |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : took evasive action |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 1000 vertical : 0 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Pilot Deviation Intra Facility Coordination Failure Operational Error |
Narrative:
Helicopter X was north of ZZZ, sbound to stadium (not lifeguard status). He called south departure radar. He was not instructed to remain outside the arsa. He was instructed to call north departure radar (me) and given a transponder code. He contacted me. I idented him (even though he was not on the correct code, and it took several transmissions to explain it to him) 4 mi northwest of ZZZ airport. We were departing runways 23L and 23R. I gave him a heading north of ZZZ (100 degrees) and told him to cross the approach end of runway 23R (his altitude -- approximately 1100 AGL). He crossed the departure end of runway 23R and an air carrier Y had to turn to avoid him. My mistake -- I had not told the tower about him (it was their airspace) because of overflt traffic and intrafac coordination workload and because I trusted him to do as I had instructed. His mistake -- even though he was legal until the point he disregarded my instructions, he didn't show much sense in flying that close to the airport at that altitude. He is a local operator and must have some idea of our operation (he had to know he was in a terrible location), or at least the correct frequency. This is not the first time, I am told, that we have had problems with the helicopters.
Original NASA ASRS Text
Title: HELI X NON ADHERENCE TO ATC INSTRUCTIONS HAD LTSS FROM ACR Y. PLTDEV. SYS ERROR.
Narrative: HELI X WAS N OF ZZZ, SBOUND TO STADIUM (NOT LIFEGUARD STATUS). HE CALLED S DEP RADAR. HE WAS NOT INSTRUCTED TO REMAIN OUTSIDE THE ARSA. HE WAS INSTRUCTED TO CALL N DEP RADAR (ME) AND GIVEN A TRANSPONDER CODE. HE CONTACTED ME. I IDENTED HIM (EVEN THOUGH HE WAS NOT ON THE CORRECT CODE, AND IT TOOK SEVERAL TRANSMISSIONS TO EXPLAIN IT TO HIM) 4 MI NW OF ZZZ ARPT. WE WERE DEPARTING RWYS 23L AND 23R. I GAVE HIM A HDG N OF ZZZ (100 DEGS) AND TOLD HIM TO CROSS THE APCH END OF RWY 23R (HIS ALT -- APPROX 1100 AGL). HE CROSSED THE DEP END OF RWY 23R AND AN ACR Y HAD TO TURN TO AVOID HIM. MY MISTAKE -- I HAD NOT TOLD THE TWR ABOUT HIM (IT WAS THEIR AIRSPACE) BECAUSE OF OVERFLT TFC AND INTRAFAC COORD WORKLOAD AND BECAUSE I TRUSTED HIM TO DO AS I HAD INSTRUCTED. HIS MISTAKE -- EVEN THOUGH HE WAS LEGAL UNTIL THE POINT HE DISREGARDED MY INSTRUCTIONS, HE DIDN'T SHOW MUCH SENSE IN FLYING THAT CLOSE TO THE ARPT AT THAT ALT. HE IS A LCL OPERATOR AND MUST HAVE SOME IDEA OF OUR OP (HE HAD TO KNOW HE WAS IN A TERRIBLE LOCATION), OR AT LEAST THE CORRECT FREQ. THIS IS NOT THE FIRST TIME, I AM TOLD, THAT WE HAVE HAD PROBLEMS WITH THE HELIS.
Data retrieved from NASA's ASRS site as of July 2007 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.