A CFI and his student fly an incorrect approach into runway 27L at oak, ca.

Attributes
ACN	518755
Time
Date	200107
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : oak.airport
State Reference	CA
Altitude	msl bound lower : 800 msl bound upper : 3200
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : o90.tracon tower : oak.tower
Operator	general aviation : instructional
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : instrument non precision
Flight Plan	IFR
Person 1
Affiliation	other
Function	instruction : instructor
Qualification	pilot : instrument pilot : atp pilot : multi engine pilot : cfi
Experience	flight time last 90 days : 100 flight time total : 4000 flight time type : 500
ASRS Report	518755
Person 2
Affiliation	other
Function	instruction : trainee
Events
Anomaly	altitude deviation : undershoot non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	aircraft equipment other aircraft equipment : ils g.s.
Resolutory Action	none taken : detected after the fact none taken : anomaly accepted
Consequence	Other
Supplementary
Problem Areas	Airport ATC Human Performance Environmental Factor Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While on a training flight to oak, we flew a 'modified' GPS approach to runway 27L at oak instead of the ILS runway 27R, sidestep runway 27L as we were cleared for. The reason for this was that we (the student and I) forgot to select 'navigation' on the #1 obs instead of 'GPS.' we had entered the GPS 27L approach in the GPS (king KLN89B) but had planned to use VOR/ILS navigation throughout this leg of the flight. However, ATC cleared us direct to sablo intersection at one point, so we entered it into the GPS and selected 'GPS' for the #1 obs. Later we received vectors for the ILS. I set the GPS on the missed approach point and the student selected 276 degrees on the obs. Both of us thinking the ILS was selected, it was in the #1 navigation radio and we idented it, but forgot to select 'navigation' on the obs. When we received our final vector for the ILS, the needle (CDI) started coming in when expected, albeit a little slow. We didn't receive the GS, which should have clued me in, but since runway 27R was closed and we were to sidestep anyway, I told the student to do the localizer only approach using DME. When we broke out at about 900 ft MSL, we were lined up for runway 27L. That is when I noticed the 'GPS' selected. After switching it showed us almost full scale left of course and below GS. An uneventful landing was made. Although we were on the GPS course, it was still in 'arm' mode, not 'active' so our sensitivity was not good enough for the GPS approach (hence my use of 'modified' earlier). Factors involved: I have been conducting and teaching GPS approachs for about 3-4 yrs and I verify the GPS button is selected. However, when not flying a GPS approach, I have not taught students to verify 'navigation' is selected. That will change now. The slow intercept and lack of GS should have alerted me to something being amiss. A recent flight to 2 other airports had navaids quit on us, so I assumed the GS out indication was the NAVAID problem too quickly -- not the pilot problem. Corrective action: future approachs using a non dedicated obs will be confirmed in the proper 'navigation' or 'GPS' mode to coincide with the approach being flown.

Original NASA ASRS Text

Title: A CFI AND HIS STUDENT FLY AN INCORRECT APCH INTO RWY 27L AT OAK, CA.

Narrative: WHILE ON A TRAINING FLT TO OAK, WE FLEW A 'MODIFIED' GPS APCH TO RWY 27L AT OAK INSTEAD OF THE ILS RWY 27R, SIDESTEP RWY 27L AS WE WERE CLRED FOR. THE REASON FOR THIS WAS THAT WE (THE STUDENT AND I) FORGOT TO SELECT 'NAV' ON THE #1 OBS INSTEAD OF 'GPS.' WE HAD ENTERED THE GPS 27L APCH IN THE GPS (KING KLN89B) BUT HAD PLANNED TO USE VOR/ILS NAV THROUGHOUT THIS LEG OF THE FLT. HOWEVER, ATC CLRED US DIRECT TO SABLO INTXN AT ONE POINT, SO WE ENTERED IT INTO THE GPS AND SELECTED 'GPS' FOR THE #1 OBS. LATER WE RECEIVED VECTORS FOR THE ILS. I SET THE GPS ON THE MISSED APCH POINT AND THE STUDENT SELECTED 276 DEGS ON THE OBS. BOTH OF US THINKING THE ILS WAS SELECTED, IT WAS IN THE #1 NAV RADIO AND WE IDENTED IT, BUT FORGOT TO SELECT 'NAV' ON THE OBS. WHEN WE RECEIVED OUR FINAL VECTOR FOR THE ILS, THE NEEDLE (CDI) STARTED COMING IN WHEN EXPECTED, ALBEIT A LITTLE SLOW. WE DIDN'T RECEIVE THE GS, WHICH SHOULD HAVE CLUED ME IN, BUT SINCE RWY 27R WAS CLOSED AND WE WERE TO SIDESTEP ANYWAY, I TOLD THE STUDENT TO DO THE LOC ONLY APCH USING DME. WHEN WE BROKE OUT AT ABOUT 900 FT MSL, WE WERE LINED UP FOR RWY 27L. THAT IS WHEN I NOTICED THE 'GPS' SELECTED. AFTER SWITCHING IT SHOWED US ALMOST FULL SCALE L OF COURSE AND BELOW GS. AN UNEVENTFUL LNDG WAS MADE. ALTHOUGH WE WERE ON THE GPS COURSE, IT WAS STILL IN 'ARM' MODE, NOT 'ACTIVE' SO OUR SENSITIVITY WAS NOT GOOD ENOUGH FOR THE GPS APCH (HENCE MY USE OF 'MODIFIED' EARLIER). FACTORS INVOLVED: I HAVE BEEN CONDUCTING AND TEACHING GPS APCHS FOR ABOUT 3-4 YRS AND I VERIFY THE GPS BUTTON IS SELECTED. HOWEVER, WHEN NOT FLYING A GPS APCH, I HAVE NOT TAUGHT STUDENTS TO VERIFY 'NAV' IS SELECTED. THAT WILL CHANGE NOW. THE SLOW INTERCEPT AND LACK OF GS SHOULD HAVE ALERTED ME TO SOMETHING BEING AMISS. A RECENT FLT TO 2 OTHER ARPTS HAD NAVAIDS QUIT ON US, SO I ASSUMED THE GS OUT INDICATION WAS THE NAVAID PROB TOO QUICKLY -- NOT THE PLT PROB. CORRECTIVE ACTION: FUTURE APCHS USING A NON DEDICATED OBS WILL BE CONFIRMED IN THE PROPER 'NAV' OR 'GPS' MODE TO COINCIDE WITH THE APCH BEING FLOWN.

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.