|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Locale Reference||navaid : vhp.vortac|
|Altitude||msl single value : 31000|
|Operator||common carrier : air carrier|
|Make Model Name||MD-88|
|Route In Use||departure sid : whitewater|
|Affiliation||company : air carrier|
|Function||flight crew : captain|
oversight : pic
|Qualification||pilot : instrument|
pilot : commercial
pilot : atp
pilot : multi engine
|Experience||flight time total : 190|
flight time type : 5000
|Anomaly||aircraft equipment problem : less severe|
non adherence : clearance
non adherence : published procedure
other spatial deviation
|Resolutory Action||controller : issued advisory|
|Problem Areas||Flight Crew Human Performance|
|Primary Problem||Flight Crew Human Performance|
|Air Traffic Incident||Pilot Deviation|
On white water 3 departure, flying from cvg to msp. Approaching vhp, controller inquired if we were going to fly over vhp (current course was going to take us about 5 mi out of vhp). We replied that the next point on our FMS was bvt he asked if vhp was depicted on the white water 3 out of cvg. We said yes it was on the commercial chart. White water 3 dated XXX, but we checked our FMS database -- and it did not show vhp between carrf and bvt. On departure from cvg when cleared to join the white water 3 departure, I (captain and PNF) executed a direct intercept leg to decee with a 294 degree course intercept. No further changes to our FMS LNAV route was done. The controller stated that this had recently happened with several other air carrier X flts and requested that we check with company about this. Controller said no traffic conflict took place, but that this error had occurred previously and somewhat screwed up their sequencing to the next center sector. In-flight, using route ii, I loaded cvg direct msp white water 2 departure, cadiz transition. Once it came up without vhp between carrf and heavy transport, the next time vhp did show up between carff and bvt.
Original NASA ASRS Text
Title: MD88 CREW DID NOT HAVE A VOR SHOWN ON THE FMC WHAT WAS LISTED ON THE PAPER SID.
Narrative: ON WHITE WATER 3 DEP, FLYING FROM CVG TO MSP. APCHING VHP, CTLR INQUIRED IF WE WERE GOING TO FLY OVER VHP (CURRENT COURSE WAS GOING TO TAKE US ABOUT 5 MI OUT OF VHP). WE REPLIED THAT THE NEXT POINT ON OUR FMS WAS BVT HE ASKED IF VHP WAS DEPICTED ON THE WHITE WATER 3 OUT OF CVG. WE SAID YES IT WAS ON THE COMMERCIAL CHART. WHITE WATER 3 DATED XXX, BUT WE CHKED OUR FMS DATABASE -- AND IT DID NOT SHOW VHP BTWN CARRF AND BVT. ON DEP FROM CVG WHEN CLRED TO JOIN THE WHITE WATER 3 DEP, I (CAPT AND PNF) EXECUTED A DIRECT INTERCEPT LEG TO DECEE WITH A 294 DEG COURSE INTERCEPT. NO FURTHER CHANGES TO OUR FMS LNAV RTE WAS DONE. THE CTLR STATED THAT THIS HAD RECENTLY HAPPENED WITH SEVERAL OTHER ACR X FLTS AND REQUESTED THAT WE CHK WITH COMPANY ABOUT THIS. CTLR SAID NO TFC CONFLICT TOOK PLACE, BUT THAT THIS ERROR HAD OCCURRED PREVIOUSLY AND SOMEWHAT SCREWED UP THEIR SEQUENCING TO THE NEXT CTR SECTOR. INFLT, USING RTE II, I LOADED CVG DIRECT MSP WHITE WATER 2 DEP, CADIZ TRANSITION. ONCE IT CAME UP WITHOUT VHP BTWN CARRF AND HVT, THE NEXT TIME VHP DID SHOW UP BTWN CARFF AND BVT.
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.