Narrative:

While still above our MDA on the GPS 4L approach to btr we received the obstacle GPWS aural warning followed by 'pull up'. I initiated a climb and the warning extinguished while we were in VMC conditions; as we could then see the runway I re-initiated descent and landed without further incident.I had briefed the approach during the descent. My first officer programed the FMS. The 4L GPS hogto fix is not in the approach data base; and so I had my first officer manually program hogto. We were subsequently vectored by ATC and then recleared to apoya; when my first officer reselected the GPS 4L approach; the FMS dropped hogto. The approach was then flown as programed and briefed with the exception that the dropped fix hogto went unnoticed and when descending to our set MDA of 700 (adjusted up from 620 on the LNAV minimum) we got our warning.not only does the FMS data base ignore hogto; the chart itself poorly depicts the hogto altitude of 820. I feel that any data base GPS approach fix on the final approach course should be included when the approach is selected. This omission proved to be a safety issue on this flight. I want to stress that my first officer and I did everything as per the [company] procedures. The approach was fully briefed and discussed; and all the checklists were complied with. The approach was conducted according to profile and was fully stabilized throughout. After landing I complained to the tower at btr and asked if they had other complaints about that approach and was told that; yes; they had had the same complaint from another carrier earlier.

Google
 

Original NASA ASRS Text

Title: The flight crew inside the FAF flying an RNAV (GPS) 4L approach to BTR using LNAV only guidance; descended below the MCA at an intermediate waypoint; HOGTO; and received an EGPWS obstacle warning. They initiated the mandated go-around but abandoned doing so when they entered VMC conditions and were able to land safely.

Narrative: While still above our MDA on the GPS 4L approach to BTR we received the obstacle GPWS aural warning followed by 'pull up'. I initiated a climb and the warning extinguished while we were in VMC conditions; as we could then see the runway I re-initiated descent and landed without further incident.I had briefed the approach during the descent. My First Officer programed the FMS. The 4L GPS HOGTO fix is not in the approach data base; and so I had my First Officer manually program HOGTO. We were subsequently vectored by ATC and then recleared to APOYA; when my First Officer reselected the GPS 4L approach; the FMS dropped HOGTO. The approach was then flown as programed and briefed with the exception that the dropped fix HOGTO went unnoticed and when descending to our set MDA of 700 (adjusted up from 620 on the LNAV minimum) we got our warning.Not only does the FMS data base ignore HOGTO; the chart itself poorly depicts the HOGTO altitude of 820. I feel that any data base GPS approach fix on the final approach course should be included when the approach is selected. This omission proved to be a safety issue on this flight. I want to stress that my First Officer and I did everything as per the [Company] procedures. The approach was fully briefed and discussed; and all the checklists were complied with. The approach was conducted according to profile and was fully stabilized throughout. After landing I complained to the Tower at BTR and asked if they had other complaints about that approach and was told that; yes; they had had the same complaint from another carrier earlier.

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