B757-200 is dispatched with database out of date. Flight crew realized enroute that a deferral was n...

Attributes
ACN	748086
Time
Date	200708
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B757-200
Operating Under FAR Part	Part 121
Flight Phase	ground : parked ground : maintenance ground : preflight
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 120 flight time total : 12000 flight time type : 4000
ASRS Report	748086
Events
Anomaly	aircraft equipment problem : less severe maintenance problem : improper documentation non adherence : company policies non adherence : far
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance Maintenance Human Performance Company
Primary Problem	Maintenance Human Performance

Narrative:

Arrived at the aircraft for departure to find unknown write-up MEL on spoilers. Looked up takeoff and landing restrs; speed restrs and altitude restr. Called dispatch to report discrepancy and asked for release to continue. Received release over radio verbally. When entering data found navigation database out of date. Called and requested maintenance to the aircraft. Maintenance asked what it was regarding; told them database. Mechanic came aboard and we showed him the database was out of date. He said 'I don't know why they didn't fix that.' the mechanic then called maintenance from the cockpit and reported to them. Maintenance told him that the plane was scheduled to be updated in ZZZ1. The mechanic told us that we were good to go. It was now departure time and the loader was standing in the plane with the manifest. We thanked the mechanic and proceeded to block 4 mins late. While en route I decided to look up in the aom to confirm what we were told by maintenance. I found that a deferral was required. I sent an ACARS to dispatch and informed them. In ZZZ2 I called dispatch and he xferred me to maintenance who gave me a crew deferral over the phone as there was no maintenance in ZZZ2. We flew the aircraft on to ZZZ1 from ZZZ2 with the deferral.

Original NASA ASRS Text

Title: B757-200 IS DISPATCHED WITH DATABASE OUT OF DATE. FLT CREW REALIZED ENROUTE THAT A DEFERRAL WAS NECESSARY FOR THIS ANOMALY.

Narrative: ARRIVED AT THE ACFT FOR DEP TO FIND UNKNOWN WRITE-UP MEL ON SPOILERS. LOOKED UP TKOF AND LNDG RESTRS; SPD RESTRS AND ALT RESTR. CALLED DISPATCH TO RPT DISCREPANCY AND ASKED FOR RELEASE TO CONTINUE. RECEIVED RELEASE OVER RADIO VERBALLY. WHEN ENTERING DATA FOUND NAV DATABASE OUT OF DATE. CALLED AND REQUESTED MAINT TO THE ACFT. MAINT ASKED WHAT IT WAS REGARDING; TOLD THEM DATABASE. MECH CAME ABOARD AND WE SHOWED HIM THE DATABASE WAS OUT OF DATE. HE SAID 'I DON'T KNOW WHY THEY DIDN'T FIX THAT.' THE MECH THEN CALLED MAINT FROM THE COCKPIT AND RPTED TO THEM. MAINT TOLD HIM THAT THE PLANE WAS SCHEDULED TO BE UPDATED IN ZZZ1. THE MECH TOLD US THAT WE WERE GOOD TO GO. IT WAS NOW DEP TIME AND THE LOADER WAS STANDING IN THE PLANE WITH THE MANIFEST. WE THANKED THE MECH AND PROCEEDED TO BLOCK 4 MINS LATE. WHILE ENRTE I DECIDED TO LOOK UP IN THE AOM TO CONFIRM WHAT WE WERE TOLD BY MAINT. I FOUND THAT A DEFERRAL WAS REQUIRED. I SENT AN ACARS TO DISPATCH AND INFORMED THEM. IN ZZZ2 I CALLED DISPATCH AND HE XFERRED ME TO MAINT WHO GAVE ME A CREW DEFERRAL OVER THE PHONE AS THERE WAS NO MAINT IN ZZZ2. WE FLEW THE ACFT ON TO ZZZ1 FROM ZZZ2 WITH THE DEFERRAL.

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.

B757-200 is dispatched with database out of date. Flight crew realized enroute that a deferral was necessary for this anomaly.