Narrative:

While executing a GPS approach to runway 5 at waukegan, il, I inadvertently started my descent too early and descended from the required 2500 ft MSL to 1420 ft MSL. As a result we were too low, too far from the airport. As soon as the error was recognized, I executed a missed approach and opted for the ILS approach to the opposite end of the runway which was completed successfully. The wind was slightly favoring the use of runway 5 and the ceiling and visibility were adequate to support using that approach. Requested from the controller that approach, and he agreed. I armed the approach mode in the FMS, although I am not well experienced in its use. My first officer was not basically familiar with the procedures for using the FMS to execute GPS approachs. After setting up the approach and receiving vectors for an intercept, the controller gave us a highspd restr of 190 KTS, then became upset when I let the speed get to 160 KTS while loading and checking the approach in the FMS. Controller then issued a turn and said he was turning us to the ILS runway 23 and mentioned 'wauke' (ILS runway 23 locator). That befuddled both pilots and we sought clarification and tried to quickly set up again for the ILS. Then he changed back to the GPS runway 5. It was thereafter on the GPS runway 5 approach that I mistook 'leesr' for the initial descent point. Moral: with an inexperienced first officer (on GPS approachs), don't do GPS approachs. More important: pay attention to the approach minimums. Callback conversation with reporter revealed the following information: reporter indicates that there was a lack of confidence in the use of the aircraft FMC by the first officer that he was flying with. There was also confusion from the approach controller regarding the specific approach that was requested. Another issue that added to the confusion was the fact that the database in the aircraft FMC did not include the same information in some cases as the approach chart. The 2 NM fix on the chart is not even in the database. Reporter indicates that he has been trying to get the discrepancies corrected locally.

Related reports:

Google
 

Original NASA ASRS Text

Title: WESTWIND PLT CONFUSED IAF ON A GPS APCH WITH THE FAF AND BEGAN DSCNT EARLY.

Narrative: WHILE EXECUTING A GPS APCH TO RWY 5 AT WAUKEGAN, IL, I INADVERTENTLY STARTED MY DSCNT TOO EARLY AND DSNDED FROM THE REQUIRED 2500 FT MSL TO 1420 FT MSL. AS A RESULT WE WERE TOO LOW, TOO FAR FROM THE ARPT. AS SOON AS THE ERROR WAS RECOGNIZED, I EXECUTED A MISSED APCH AND OPTED FOR THE ILS APCH TO THE OPPOSITE END OF THE RWY WHICH WAS COMPLETED SUCCESSFULLY. THE WIND WAS SLIGHTLY FAVORING THE USE OF RWY 5 AND THE CEILING AND VISIBILITY WERE ADEQUATE TO SUPPORT USING THAT APCH. REQUESTED FROM THE CTLR THAT APCH, AND HE AGREED. I ARMED THE APCH MODE IN THE FMS, ALTHOUGH I AM NOT WELL EXPERIENCED IN ITS USE. MY FO WAS NOT BASICALLY FAMILIAR WITH THE PROCS FOR USING THE FMS TO EXECUTE GPS APCHS. AFTER SETTING UP THE APCH AND RECEIVING VECTORS FOR AN INTERCEPT, THE CTLR GAVE US A HIGHSPD RESTR OF 190 KTS, THEN BECAME UPSET WHEN I LET THE SPD GET TO 160 KTS WHILE LOADING AND CHKING THE APCH IN THE FMS. CTLR THEN ISSUED A TURN AND SAID HE WAS TURNING US TO THE ILS RWY 23 AND MENTIONED 'WAUKE' (ILS RWY 23 LOCATOR). THAT BEFUDDLED BOTH PLTS AND WE SOUGHT CLARIFICATION AND TRIED TO QUICKLY SET UP AGAIN FOR THE ILS. THEN HE CHANGED BACK TO THE GPS RWY 5. IT WAS THEREAFTER ON THE GPS RWY 5 APCH THAT I MISTOOK 'LEESR' FOR THE INITIAL DSCNT POINT. MORAL: WITH AN INEXPERIENCED FO (ON GPS APCHS), DON'T DO GPS APCHS. MORE IMPORTANT: PAY ATTN TO THE APCH MINIMUMS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR INDICATES THAT THERE WAS A LACK OF CONFIDENCE IN THE USE OF THE ACFT FMC BY THE FO THAT HE WAS FLYING WITH. THERE WAS ALSO CONFUSION FROM THE APCH CTLR REGARDING THE SPECIFIC APCH THAT WAS REQUESTED. ANOTHER ISSUE THAT ADDED TO THE CONFUSION WAS THE FACT THAT THE DATABASE IN THE ACFT FMC DID NOT INCLUDE THE SAME INFO IN SOME CASES AS THE APCH CHART. THE 2 NM FIX ON THE CHART IS NOT EVEN IN THE DATABASE. RPTR INDICATES THAT HE HAS BEEN TRYING TO GET THE DISCREPANCIES CORRECTED LOCALLY.

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.