37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 839316 |
Time | |
Date | 200906 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | BUR.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Route In Use | SID VNY7 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | First Officer |
Experience | Flight Crew Last 90 Days 297 Flight Crew Type 4000 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Other / Unknown |
Narrative:
While loading the flight plan; I noted the fix twine would not load by either manually selecting the SID and transition or using the company route method. I called dispatch per fom (which says not to load points that do not load themselves); dispatch said; 'I can't do anything for you.' I said thanks and hung up; called clearance and worked out a plan to fly direct gmn after radar vectors on departure. FMC database did not show proper points for SID. Come up with a better plan on how to verify FMC database loads for accuracy. Delete fom requirement to call dispatch; as they did nothing to resolve the problem. Allow pilots to once verifying proper fix is loaded; to go per flight plan.
Original NASA ASRS Text
Title: B737 First Officer reported waypoint TWINE on the VNY7 departure from BUR will not load when the SID is loaded into the FMC or when the company route is inserted from FMC memory.
Narrative: While loading the flight plan; I noted the fix TWINE would not load by either manually selecting the SID and transition or using the Company route method. I called Dispatch per FOM (which says not to load points that do not load themselves); Dispatch said; 'I can't do anything for you.' I said thanks and hung up; called Clearance and worked out a plan to fly direct GMN after radar vectors on departure. FMC database did not show proper points for SID. Come up with a better plan on how to verify FMC database loads for accuracy. Delete FOM requirement to call Dispatch; as they did nothing to resolve the problem. Allow Pilots to once verifying proper fix is loaded; to go per flight plan.
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.