37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 811934 |
Time | |
Date | 200811 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : ind.airport |
State Reference | IN |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : zzz.tower |
Operator | common carrier : air carrier |
Make Model Name | EMB ERJ 145 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 811934 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | non adherence : clearance non adherence : far other spatial deviation |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | none taken : anomaly accepted |
Supplementary | |
Problem Areas | Chart Or Publication Company Maintenance Human Performance |
Primary Problem | Chart Or Publication |
Narrative:
During climb proceeding direct mzz; we realized the STAR loaded in the PF's (first officer's) FMS was the ROYKO3; not the ROYKO2. We put in the correct STAR and verified the fixes with our charts. ATC had cleared us direct mzz; direct royko; direct bearz and we continued the flight with no further issues. I had verified the FMS database had not expired during preflight as required. The effective date of the royko 3 is in 7 days. Why it was in the current database; I have no idea. I contacted chief pilot office as well as safety since I had just viewed his good STAR presentation. I spoke with chief pilot and he informed me other aircraft had similar problem. Possible closer verification of the date of the FMS database; instead of only verifying it's not expired and current. Why would a database be activated in one of our aircraft before it should be? We received guidance today from the company about this. I'll definitely be checking all databases for the exact date. Another aircraft was found this morning with the same issue.
Original NASA ASRS Text
Title: EMB145 FLIGHT CREW DISCOVERS THE FIRST OFFICERS FMS DATABASE CONTAINED A SID THAT WAS NOT EFFECTIVE FOR SEVEN MORE DAYS.
Narrative: DURING CLB PROCEEDING DIRECT MZZ; WE REALIZED THE STAR LOADED IN THE PF'S (FO'S) FMS WAS THE ROYKO3; NOT THE ROYKO2. WE PUT IN THE CORRECT STAR AND VERIFIED THE FIXES WITH OUR CHARTS. ATC HAD CLRED US DIRECT MZZ; DIRECT ROYKO; DIRECT BEARZ AND WE CONTINUED THE FLT WITH NO FURTHER ISSUES. I HAD VERIFIED THE FMS DATABASE HAD NOT EXPIRED DURING PREFLT AS REQUIRED. THE EFFECTIVE DATE OF THE ROYKO 3 IS IN 7 DAYS. WHY IT WAS IN THE CURRENT DATABASE; I HAVE NO IDEA. I CONTACTED CHIEF PLT OFFICE AS WELL AS SAFETY SINCE I HAD JUST VIEWED HIS GOOD STAR PRESENTATION. I SPOKE WITH CHIEF PLT AND HE INFORMED ME OTHER ACFT HAD SIMILAR PROB. POSSIBLE CLOSER VERIFICATION OF THE DATE OF THE FMS DATABASE; INSTEAD OF ONLY VERIFYING IT'S NOT EXPIRED AND CURRENT. WHY WOULD A DATABASE BE ACTIVATED IN ONE OF OUR ACFT BEFORE IT SHOULD BE? WE RECEIVED GUIDANCE TODAY FROM THE COMPANY ABOUT THIS. I'LL DEFINITELY BE CHKING ALL DATABASES FOR THE EXACT DATE. ANOTHER ACFT WAS FOUND THIS MORNING WITH THE SAME ISSUE.
Data retrieved from NASA's ASRS site as of May 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.