Narrative:

I was the pilot flying into san diego. Based on the ATIS; I briefed a visual approach with a backup of the localizer runway 27. Approaching vydda if; we were cleared the localizer runway 27 at 4;000. I performed a level change to descend to 4;000 from 5;000; not wanting to get rushed on the approach. Passing vydda; I set 1;800 (FAF altitude); started slowing down; confirmed the MDA; then set 680 ft; pilot not flying confirmed. I did not reselect prof; or say 'prof's available to 680.' approach told us to maintain at or above 170 KTS till reebo (FAF). I started configuring at 12 DME with slats; F15; gear; F28; F35. My cross-check was focused on flight director; and RA to ensure that we were stable by 1;000. Pilot not flying stated that he could see the runway. I looked up and could see it but couldn't verify PAPI. Pilot not flying stated we were low and directed a climb. Tower reported that we had crossed reebo low. I intercepted the PAPI glidepath from below and performed a normal landing. We conducted a thorough post flight assessment and debrief. The error was caused by my (pilot flying) failure to select and confirm 'prof'. Subsequently; I configured late for this type of procedure. This rushed me and added to my fixation on radar altimeter and configuration/speed. I dropped out my positional awareness in regards to crossing altitudes. 1. I should have reviewed and briefed the 'high threat' non-ILS approach earlier. Since we don't fly these approaches very often a thorough review of qrc (not current) and flight manual bulletin procedures should have been accomplished. Don't forget to brief vdp. 2. Double; triple check 'prof' and altitude settings. 3. Configure early!!! This allows for proper cross check and helps eliminate fixation. 4. Don't ever get lulled into 'it's going to be a visual approach'.

Related reports:

Google
 

Original NASA ASRS Text

Title: MD11 flight crew reports descending below the FAF altitude at REEBO during the LOC Runway 27 approach to SAN due to inattention and not using the PROF autoflight function. The Tower and the pilot not flying both take notice and the approach path is corrected to the PAPI's and a visual approach clearance is issued.

Narrative: I was the pilot flying into San Diego. Based on the ATIS; I briefed a visual approach with a backup of the LOC Runway 27. Approaching VYDDA IF; we were cleared the LOC Runway 27 at 4;000. I performed a level change to descend to 4;000 from 5;000; not wanting to get rushed on the approach. Passing VYDDA; I set 1;800 (FAF altitude); started slowing down; confirmed the MDA; then set 680 FT; pilot not flying confirmed. I did not reselect PROF; or SAY 'PROF's available to 680.' Approach told us to maintain at or above 170 KTS till REEBO (FAF). I started configuring at 12 DME with slats; F15; gear; F28; F35. My cross-check was focused on Flight Director; and RA to ensure that we were stable by 1;000. Pilot not flying stated that he could see the runway. I looked up and could see it but couldn't verify PAPI. Pilot not flying stated we were low and directed a climb. Tower reported that we had crossed REEBO low. I intercepted the PAPI glidepath from below and performed a normal landing. We conducted a thorough post flight assessment and debrief. The error was caused by my (pilot flying) failure to select and confirm 'PROF'. Subsequently; I configured late for this type of procedure. This rushed me and added to my fixation on radar altimeter and configuration/speed. I dropped out my positional awareness in regards to crossing altitudes. 1. I should have reviewed and briefed the 'high threat' non-ILS approach earlier. Since we don't fly these approaches very often a thorough review of QRC (not current) and Flight Manual Bulletin procedures should have been accomplished. Don't forget to brief VDP. 2. Double; triple check 'PROF' and altitude settings. 3. Configure EARLY!!! This allows for proper cross check and helps eliminate fixation. 4. Don't ever get lulled into 'it's going to be a visual approach'.

Data retrieved from NASA's ASRS site as of July 2013 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.