Narrative:

After radar vectors, told to join V8 and resume own navigation. Set 'from' radial into obs and failed to intercept crossing airway. Was using LORAN as backup, however V8 had not been set into LORAN because route contained unnamed intxns and flying single pilot IFR, did not want to calculate intxns in-flight. Pilot error, confused 'from' radial with 'to' bearing. Will try to use better common sense, situational awareness and correct chart reading. Suggest that with the wide availability of RNAV, LORAN and GPS, it would be helpful to have all intxns ATC uses named and in databases to facilitate their entry. Had the intersection of V8 and V363 between pdz, prado, aheim and jogit been in the database, route could have been quickly and easily entered into the LORAN and GPS flight plans and the error would have been instantly obvious.

Google
 

Original NASA ASRS Text

Title: SMA MISSETS VOR OBS RESULTS IN THE HDG DEV.

Narrative: AFTER RADAR VECTORS, TOLD TO JOIN V8 AND RESUME OWN NAV. SET 'FROM' RADIAL INTO OBS AND FAILED TO INTERCEPT XING AIRWAY. WAS USING LORAN AS BACKUP, HOWEVER V8 HAD NOT BEEN SET INTO LORAN BECAUSE RTE CONTAINED UNNAMED INTXNS AND FLYING SINGLE PLT IFR, DID NOT WANT TO CALCULATE INTXNS INFLT. PLT ERROR, CONFUSED 'FROM' RADIAL WITH 'TO' BEARING. WILL TRY TO USE BETTER COMMON SENSE, SITUATIONAL AWARENESS AND CORRECT CHART READING. SUGGEST THAT WITH THE WIDE AVAILABILITY OF RNAV, LORAN AND GPS, IT WOULD BE HELPFUL TO HAVE ALL INTXNS ATC USES NAMED AND IN DATABASES TO FACILITATE THEIR ENTRY. HAD THE INTXN OF V8 AND V363 BTWN PDZ, PRADO, AHEIM AND JOGIT BEEN IN THE DATABASE, RTE COULD HAVE BEEN QUICKLY AND EASILY ENTERED INTO THE LORAN AND GPS FLT PLANS AND THE ERROR WOULD HAVE BEEN INSTANTLY OBVIOUS.

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.