Narrative:

The flight was dispatched and flown to bogota. Soa VOR was NOTAM'd out of service. The NOTAM was only posted in the bogota center NOTAMS on page 52 of the 54-page release. There was no NOTAM reference: soa in the skbo airport section. Soa is a required NAVAID to fly any approach to runways 31L/right. Therefore; I was dispatched to an airport that with slightly stronger winds from the west I would not have been able to land at. Though I read all the NOTAMS in the 54-page release; I missed that one on page 52; during my preflight. I called dispatch for a briefing and was not told about any NAVAID or approach problems. During cruise; I further studied the release and discovered my oversight.the VOR has been out of service since late april. When I landed in skbo; I called dispatch to discuss how this was going to impact the departure procedure; which also utilizes soa. Dispatch told me that they knew soa was out of service and that the director of a third party provider dispatch said we can fly the departure with DME IRU; despite no such note on the plate.the most disturbing thing to me is that they knew that if the airport turned around to 31; I would have to divert; and never thought it was important information to share with the crew.suggestions: on how to correct the reported concern? Hire competent dispatchers and train them. Filter the ridiculous amount of NOTAMS that we must read before departure. It's impossible to put the time in necessary to study the vast amount of NOTAMS and determine the impact on operations. We have pages and pages of obstacle NOTAMS that we don't need to see because aerodata factors them into the data. There were pages and pages of NOTAMS that only affect VFR operations. There are often NOTAMS to centers we could not possibly even reach with fuel onboard. When dispatch knows that a VOR that may be required to complete the flight; the must notify the crew.additionally; the dispatchers should be trained on how to brief the captains on a flight. Typically; I have to do my own preparation; use my own resources to find weather and NOTAMS before I arrive at the aircraft in an attempt to get a better idea of the challenges ahead. When I call dispatch; they know nothing; and can barely answer the questions I pose to them. Do not allow a third party provide dispatch services to an airline. The third party dispatch is totally incompetent in everything they do. Whenever I speak to a dispatcher; it is clear that they are just guessing and have no idea how details affect operations. I often find myself surrounded by thunderstorms and they say the weather is clear. They do not honor requests for specific takeoff landing report (tlr) data because they don't understand why I want it. I even had one hang up on me; when I pointed out that there was a tornado warning at the airport and he doesn't know this because his company does not provide him the resources he needs.

Related reports:

Google
 

Original NASA ASRS Text

Title: B767 Captain reported being dispatched to an airport without a complete NOTAM briefing from the Dispatcher; which would have dire consequence and a possible diversion at their destination.

Narrative: The flight was dispatched and flown to Bogota. SOA VOR was NOTAM'd out of service. The NOTAM was only posted in the Bogota center NOTAMS on page 52 of the 54-page release. There was no NOTAM reference: SOA in the SKBO airport section. SOA is a required NAVAID to fly any approach to runways 31L/R. Therefore; I was dispatched to an airport that with slightly stronger winds from the west I would not have been able to land at. Though I read all the NOTAMS in the 54-page release; I missed that one on page 52; during my preflight. I called dispatch for a briefing and was not told about any NAVAID or approach problems. During cruise; I further studied the release and discovered my oversight.The VOR has been out of service since late April. When I landed in SKBO; I called dispatch to discuss how this was going to impact the departure procedure; which also utilizes SOA. Dispatch told me that they knew SOA was out of service and that the director of a third party provider dispatch said we can fly the departure with DME IRU; despite no such note on the plate.The most disturbing thing to me is that THEY KNEW that if the airport turned around to 31; I would have to divert; and never thought it was important information to share with the crew.Suggestions: on how to correct the reported concern? Hire competent dispatchers and train them. Filter the ridiculous amount of NOTAMS that we must read before departure. It's impossible to put the time in necessary to study the vast amount of NOTAMS and determine the impact on operations. We have pages and pages of obstacle NOTAMS that we don't need to see because Aerodata factors them into the data. There were pages and pages of NOTAMS that only affect VFR operations. There are often NOTAMS to centers we could not possibly even reach with fuel onboard. When dispatch knows that a VOR that may be required to complete the flight; the MUST NOTIFY the crew.Additionally; the dispatchers should be trained on how to brief the captains on a flight. Typically; I have to do my own preparation; use my own resources to find weather and NOTAMS before I arrive at the aircraft in an attempt to get a better idea of the challenges ahead. When I call dispatch; they know nothing; and can barely answer the questions I pose to them. Do not allow a third party provide dispatch services to an airline. The third party Dispatch is totally incompetent in everything they do. Whenever I speak to a dispatcher; it is clear that they are just guessing and have no idea how details affect operations. I often find myself surrounded by thunderstorms and they say the weather is clear. They do not honor requests for specific Takeoff Landing Report (TLR) data because they don't understand why I want it. I even had one hang up on me; when I pointed out that there was a Tornado warning at the airport and he doesn't know this because his company does not provide him the resources he needs.

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.