A300 crew reports flo VOR position error in navigation database.

Attributes
ACN	709031
Time
Date	200609
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : flo.vortac
State Reference	FL
Altitude	msl single value : 31000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zjx.artcc
Operator	common carrier : air carrier
Make Model Name	A300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	cruise : level
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 150 flight time total : 10000 flight time type : 6371
ASRS Report	709031
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	aircraft equipment problem : less severe non adherence : clearance other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance flight crew : returned to intended or assigned course
Consequence	other
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Aircraft

Narrative:

During new clearance to flo; the flo location did not match map. While turning; the aircraft rolled out to a heading that would have gone to correct location for flo. FMC #1 and #2 no warnings or cautions. Heading select used to get navigation deselected. Aircraft with ATC assistance put on proper course to flo since out of VOR range. Actual aircraft heading verified with ARTCC to be 20 degrees to far right for flo. Aircraft database current on both FMC's. Callback conversation with reporter acn 709036 revealed the following information: the captain reports that he has many yrs experience on the A300 and that crew error is not a factor here. The database was current and the IRS was operating normally. His conclusion is that the database was corrupted or had an error in production. Maintenance reloaded the current database as a signoff for the logbook write-up.

Original NASA ASRS Text

Title: A300 CREW RPTS FLO VOR POS ERROR IN NAV DATABASE.

Narrative: DURING NEW CLRNC TO FLO; THE FLO LOCATION DID NOT MATCH MAP. WHILE TURNING; THE ACFT ROLLED OUT TO A HDG THAT WOULD HAVE GONE TO CORRECT LOCATION FOR FLO. FMC #1 AND #2 NO WARNINGS OR CAUTIONS. HDG SELECT USED TO GET NAV DESELECTED. ACFT WITH ATC ASSISTANCE PUT ON PROPER COURSE TO FLO SINCE OUT OF VOR RANGE. ACTUAL ACFT HDG VERIFIED WITH ARTCC TO BE 20 DEGS TO FAR R FOR FLO. ACFT DATABASE CURRENT ON BOTH FMC'S. CALLBACK CONVERSATION WITH RPTR ACN 709036 REVEALED THE FOLLOWING INFO: THE CAPT RPTS THAT HE HAS MANY YRS EXPERIENCE ON THE A300 AND THAT CREW ERROR IS NOT A FACTOR HERE. THE DATABASE WAS CURRENT AND THE IRS WAS OPERATING NORMALLY. HIS CONCLUSION IS THAT THE DATABASE WAS CORRUPTED OR HAD AN ERROR IN PRODUCTION. MAINT RELOADED THE CURRENT DATABASE AS A SIGNOFF FOR THE LOGBOOK WRITE-UP.

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