Heading track deviation during IAP VOR a approach into hwd.

Attributes
ACN	316222
Time
Date	199509
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : oak airport : hwd
State Reference	CA
Altitude	msl bound lower : 900 msl bound upper : 3000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : oak tower : hwd tower : sea
Operator	other
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	descent : approach landing : missed approach
Route In Use	enroute : on vectors enroute other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 25 flight time total : 1800 flight time type : 50
ASRS Report	316222
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : published procedure non adherence : far non adherence : clearance non adherence other other anomaly other other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : exited penetrated airspace other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

In sum: reporter was on an IAP VOR a approach to hwd, planning on getting VMC under the 1000 ft broken deck and proceeding VMC to sql. He got behind the aircraft and was distracted by approach controller asking if he was 'tracking the localizer into hwd.' he dialed in the ILS (which he couldn't use for the approach as it required a DME which he did not have) to verify. He then tuned in his xchk radial for the FAF, realizing he was past it but 'estimating' and then starting a time to map. He guessed wrong and overshot that point, getting very close to oak class B airspace. He reported a marker on the approach, making the controller think that he was deliberately making an approach to oak airport, as the marker was the LOM at oak. Reporter cites 'confusing remarks and instructions' (which related to his actual, but unknown, position) from the controllers as adding to his loss of situational awareness. He admits his poor performance and says that he should have asked for vectors for another approach much sooner. As it was, he ended up with controller sponsored vectors, a missed approach and a second, successful approach.

Original NASA ASRS Text

Title: HDG TRACK DEV DURING IAP VOR A APCH INTO HWD.

Narrative: IN SUM: RPTR WAS ON AN IAP VOR A APCH TO HWD, PLANNING ON GETTING VMC UNDER THE 1000 FT BROKEN DECK AND PROCEEDING VMC TO SQL. HE GOT BEHIND THE ACFT AND WAS DISTRACTED BY APCH CTLR ASKING IF HE WAS 'TRACKING THE LOC INTO HWD.' HE DIALED IN THE ILS (WHICH HE COULDN'T USE FOR THE APCH AS IT REQUIRED A DME WHICH HE DID NOT HAVE) TO VERIFY. HE THEN TUNED IN HIS XCHK RADIAL FOR THE FAF, REALIZING HE WAS PAST IT BUT 'ESTIMATING' AND THEN STARTING A TIME TO MAP. HE GUESSED WRONG AND OVERSHOT THAT POINT, GETTING VERY CLOSE TO OAK CLASS B AIRSPACE. HE RPTED A MARKER ON THE APCH, MAKING THE CTLR THINK THAT HE WAS DELIBERATELY MAKING AN APCH TO OAK ARPT, AS THE MARKER WAS THE LOM AT OAK. RPTR CITES 'CONFUSING REMARKS AND INSTRUCTIONS' (WHICH RELATED TO HIS ACTUAL, BUT UNKNOWN, POS) FROM THE CTLRS AS ADDING TO HIS LOSS OF SITUATIONAL AWARENESS. HE ADMITS HIS POOR PERFORMANCE AND SAYS THAT HE SHOULD HAVE ASKED FOR VECTORS FOR ANOTHER APCH MUCH SOONER. AS IT WAS, HE ENDED UP WITH CTLR SPONSORED VECTORS, A MISSED APCH AND A SECOND, SUCCESSFUL APCH.

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.