37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 858604 |
Time | |
Date | 200910 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PHX.Airport |
State Reference | AZ |
Aircraft 1 | |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Climb |
Route In Use | SID SJN5 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Not Flying First Officer |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
Departing phx runway 25R; st. Johns five departure. Review of the waypoints on the ground shows that forpe intersection is missing; in spite of 3 attempts to load the runway; SID; and transition. Captain and I discussed this; knowing we would be cleared direct forpe by departure. We decided we could type it in if need be. Sure enough - after takeoff; 'go direct to forpe.' when the intersection is typed into the scratchpad and moved to line 1L; it replicates itself - with a discontinuity - like this: line 1...forpe; line 2...discont; line 3...forpe; line 4...sjn (and the rest of the route). I have seen this before on a previous phx departure. I believe this is some kind of database anomaly. I have no uncertainty about the sequence of events I have described.
Original NASA ASRS Text
Title: MD80 First Officer reports that FORPE intersection does not load when the SJN5 from PHX Runway 25R is selected in the FMS. When manually entered it replicates itself with a route discontinuity in between.
Narrative: Departing PHX Runway 25R; St. Johns Five departure. Review of the waypoints on the ground shows that FORPE intersection is missing; in spite of 3 attempts to load the runway; SID; and transition. Captain and I discussed this; knowing we would be cleared direct FORPE by departure. We decided we could type it in if need be. Sure enough - after takeoff; 'go direct to FORPE.' When the intersection is typed into the scratchpad and moved to Line 1L; it replicates itself - with a discontinuity - like this: Line 1...FORPE; Line 2...DISCONT; Line 3...FORPE; Line 4...SJN (and the rest of the route). I have seen this before on a previous PHX departure. I believe this is some kind of database anomaly. I have no uncertainty about the sequence of events I have described.
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.