MD80 captain discovers that the runway transitions for the honie 7 RNAV arrival are not in his data ...

Narrative:

This flight was a part 91 reposition to atl. After an aircraft swap we took off and all was normal. ATC issued a reroute into atl via present position direct goons intersection for the honie 7 RNAV arrival into atlanta. We loaded the flight plan into the FMS and checked it up until the wolmn intersection. The FMS built the arrival to this point because after this point the arrival branches off depending on which runway you are landing. Five miles outside this point we were told to contact atlanta approach. We did and were assigned runway 26R. We loaded that in the box thinking this would build the rest of the arrival; it did not. We tried again to no avail. Then we just typed in nofiv which is the next fix we should be going to for 26R. It then told us 'not in data base.' we then built a fix just to turn in the proper direction and advised atlanta approach these fixes were not in our data base. It was busy there was weather closing in on the field and they assigned us a heading. We were then given a frequency change and were asked to proceed to havad and it to was not in the data base and again over a very busy frequency had to explain that is not in our data base. Again grudgingly we were assigned another heading. We landed normally and never heard anything from the tower about any action to be taken.when we put in a runway the FMS and it did not finish building the arrival as it should have. The event occurred because not all the arrival for the honie 7 RNAV arrival into atlanta is in the FMS database. There is no indication when you load the arrival that not all of it is in the box. It is a named arrival in FMS but is incomplete with its data. We should not file RNAV arrivals or departures until we are sure they are in the FMS database properly. On the way home I played with the FMS to see if some of the chicago RNAV departure points were in this box. They were also not in the box. Of the 8 arrival fixes after the wolmn intersection on the honie 7 only one of them is in the box.

Original NASA ASRS Text

Title: MD80 Captain discovers that the runway transitions for the HONIE 7 RNAV arrival are not in his data base and requests vectors from ATC. On the next leg other waypoint discrepancies were noted.

Narrative: This flight was a Part 91 reposition to ATL. After an aircraft swap we took off and all was normal. ATC issued a reroute into ATL via present position direct GOONS Intersection for the HONIE 7 RNAV arrival into Atlanta. We loaded the flight plan into the FMS and checked it up until the WOLMN Intersection. The FMS built the arrival to this point because after this point the arrival branches off depending on which runway you are landing. Five miles outside this point we were told to contact Atlanta Approach. We did and were assigned Runway 26R. We loaded that in the box thinking this would build the rest of the arrival; it did not. We tried again to no avail. Then we just typed in NOFIV which is the next fix we should be going to for 26R. It then told us 'NOT IN DATA BASE.' We then built a fix just to turn in the proper direction and advised Atlanta Approach these fixes were not in our data base. It was busy there was weather closing in on the field and they assigned us a heading. We were then given a frequency change and were asked to proceed to HAVAD and it to was not in the data base and again over a very busy frequency had to explain that is not in our data base. Again grudgingly we were assigned another heading. We landed normally and never heard anything from the Tower about any action to be taken.When we put in a runway the FMS and it did not finish building the arrival as it should have. The event occurred because not all the arrival for the HONIE 7 RNAV arrival into Atlanta is in the FMS database. There is no indication when you load the arrival that not all of it is in the box. It is a named arrival in FMS but is incomplete with its data. We should not file RNAV arrivals or departures until we are sure they are in the FMS database properly. On the way home I played with the FMS to see if some of the Chicago RNAV departure points were in this box. They were also not in the box. Of the 8 arrival fixes after the WOLMN Intersection on the HONIE 7 only one of them is in the box.

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.

Attributes
ACN	954535
Time
Date	201106
Local Time Of Day	1201-1800
Place
Locale Reference	A80.TRACON
State Reference	GA
Aircraft 1
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	Descent
Route In Use	STAR HONIE 7
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

MD80 captain discovers that the runway transitions for the honie 7 RNAV arrival are not in his data base and requests vectors from ATC. On the next leg other waypoint discrepancies were noted.