Narrative:

Bogota approach cleared us for the VOR-C approach; to land on runway 31R; due to northerly winds at skbo. All FMC approaches are for landing runway 13. The ipad has a VOR-C jeppesen chart but would have required QRH raw data approach procedures.ATC refused my requests to land south with a tailwind.I made the decision that to fly the VOR-C procedure in IMC was unsafe for the following reasons:-I have never practiced nor flown a raw data approach in almost 5;000hrs of 737 time.-skbo is a mountainous terrain airport designated as special per 14 crash fire rescue equipment 121.445. Flying approach procedures IMC into this airport; that I have never used; is unsafe.-the engine out missed approach for runway 31L requires the existence of a 'route 2' in the FMC; per jeppesen page 10-7e-2; that cannot be flown legally on non-route 2 equipped aircraft. I am quite sure we have not even taken delivery on any route 2 equipped 737's...........this issue needs to be addressed on our fleet since; apart from this event; the missed app procedure for all runways requires a route 2; installed in the FMC; to perform the single engine missed approach correctly.-the VOR missed approach to the northeast via zip VOR; although at first glance might be ok for single engine missed approach; I was not comfortable not having specific 10-7 page guidance indicating a single engine missed was safe in that direction from the missed app point that was located a couple of miles east of the airport.I informed ATC that I would only accept the VOR-C procedure if we could maintain VMC from the minimum vectoring altitude (MVA) on the approach to landing.we were able to maintain VMC and fly the VOR-C as published to a circle and land on runway 31L.ATC informed the aeronautical civil authorities of our difficulties accepting the approach. We were met and debriefed by 3 representatives of the aeronautical civil agency. I explained to them our procedures; my concerns and the FMC database issue.

Google
 

Original NASA ASRS Text

Title: The crew expressed concerns about the BOG VOR-C 31R/31L approach at SKBO; as it is not in the FMS database and is used infrequently. There were also questions about missed approach performance.

Narrative: Bogota approach cleared us for the VOR-C approach; to land on Runway 31R; due to northerly winds at SKBO. All FMC approaches are for landing Runway 13. The iPad has a VOR-C Jeppesen chart but would have required QRH raw data approach procedures.ATC refused my requests to land south with a tailwind.I made the decision that to fly the VOR-C procedure in IMC was unsafe for the following reasons:-I have never practiced nor flown a raw data approach in almost 5;000hrs of 737 time.-SKBO is a mountainous terrain airport designated as special per 14 CFR 121.445. Flying approach procedures IMC into this airport; that I have never used; is unsafe.-The engine out missed approach for Runway 31L requires the existence of a 'route 2' in the FMC; per jeppesen page 10-7e-2; that cannot be flown legally on non-route 2 equipped aircraft. I am quite sure we have not even taken delivery on any route 2 equipped 737's...........this issue needs to be addressed on our fleet since; apart from this event; the missed app procedure for ALL runways requires a route 2; installed in the FMC; to perform the Single Engine missed approach correctly.-The VOR missed approach to the northeast via ZIP VOR; although at first glance might be ok for Single Engine missed approach; I was not comfortable not having specific 10-7 page guidance indicating a Single Engine missed was safe in that direction from the missed app point that was located a couple of miles east of the airport.I informed ATC that I would only accept the VOR-C procedure if we could maintain VMC from the Minimum Vectoring Altitude (MVA) on the approach to landing.We were able to maintain VMC and fly the VOR-C as published to a circle and land on Runway 31L.ATC informed the Aeronautical Civil authorities of our difficulties accepting the approach. We were met and debriefed by 3 representatives of the Aeronautical Civil agency. I explained to them our procedures; my concerns and the FMC database issue.

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