 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot of an small transport turboprop intercepted the VOR radial to which ATC had cleared him on a heading. Departure controller intervened and advised that he was supposed to remain on heading rather than turning onto and intercepting the VOR radial.
| Attributes | |
| ACN | 431204 |
| Time | |
| Date | 199903 |
| Day | Tue |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | navaid : mzb.vortac |
| State Reference | CA |
| Altitude | msl single value : 10000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : sct.tracon |
| Operator | general aviation : personal |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | other vortac |
| Flight Phase | climbout : intermediate altitude |
| Route In Use | departure : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 95 flight time total : 6800 flight time type : 400 |
| ASRS Report | 431201 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : departure |
| Qualification | controller : radar |
| Events | |
| Anomaly | non adherence : far non adherence : clearance other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued alert none taken : detected after the fact |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance ATC Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
ATC at myf issued me an IFR clearance to 'fly heading 270 degrees after takeoff to the mission bay 300 degree radial.' upon climbing out, I flew the heading until I was on centerline of the radial and intercepted the course. 30 seconds later the departure controller said to 'fly heading 270 degrees.' there was no traffic conflict and very few if any aircraft on the frequency. I feel that the clearance as issued was confusing. If I was expected to remain on the vector on 270 degrees, and was not expected to intercept the 300 degree radial of mission bay VOR, then the issuing controller should state 'expect the 300 degree radial' not 'fly heading 270 degrees for the 300 degree radial of mzb VOR.' the controller of departure said, 'he must/should have stated, fly 270 degree vector for the 300 degree radial of mission bay.' again no conflict arose and the controller was amiable, but I feel this is a confusing clearance issuance.
Original NASA ASRS Text
Title: PLT OF AN SMT TURBOPROP INTERCEPTED THE VOR RADIAL TO WHICH ATC HAD CLRED HIM ON A HDG. DEP CTLR INTERVENED AND ADVISED THAT HE WAS SUPPOSED TO REMAIN ON HDG RATHER THAN TURNING ONTO AND INTERCEPTING THE VOR RADIAL.
Narrative: ATC AT MYF ISSUED ME AN IFR CLRNC TO 'FLY HDG 270 DEGS AFTER TKOF TO THE MISSION BAY 300 DEG RADIAL.' UPON CLBING OUT, I FLEW THE HDG UNTIL I WAS ON CTRLINE OF THE RADIAL AND INTERCEPTED THE COURSE. 30 SECONDS LATER THE DEP CTLR SAID TO 'FLY HDG 270 DEGS.' THERE WAS NO TFC CONFLICT AND VERY FEW IF ANY ACFT ON THE FREQ. I FEEL THAT THE CLRNC AS ISSUED WAS CONFUSING. IF I WAS EXPECTED TO REMAIN ON THE VECTOR ON 270 DEGS, AND WAS NOT EXPECTED TO INTERCEPT THE 300 DEG RADIAL OF MISSION BAY VOR, THEN THE ISSUING CTLR SHOULD STATE 'EXPECT THE 300 DEG RADIAL' NOT 'FLY HDG 270 DEGS FOR THE 300 DEG RADIAL OF MZB VOR.' THE CTLR OF DEP SAID, 'HE MUST/SHOULD HAVE STATED, FLY 270 DEG VECTOR FOR THE 300 DEG RADIAL OF MISSION BAY.' AGAIN NO CONFLICT AROSE AND THE CTLR WAS AMIABLE, BUT I FEEL THIS IS A CONFUSING CLRNC ISSUANCE.
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.