 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Emb-145 captain reported an anomaly with his honeywell FMS. When changing runway assignment on arrival to ric the FMS loaded the waypoint spidr twice.
| Attributes | |
| ACN | 1242249 |
| Time | |
| Date | 201502 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | PCT.TRACON |
| State Reference | VA |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 145 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR SPIDR1 |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe |
Narrative:
We were originally cleared to richmond via flight planned routing to the mol transition of the SPIDR1 arrival. The honeywell FMS doesn't allow you to load the SPIDR1 arrival until you've chosen a landing runway; so while I was loading the FMS prior to departure I selected runway 20 and verified the fixes were correct with the chart. While flying the arrival just prior to redng; we contacted potomac approach and they assigned runway 16 so I changed the runway in the FMS to match. Our jumpseater noticed that after I did this the flight plan in the FMS showed spidr twice between hemme and deeer. Also; when we crossed over spidr the flight guidance went in to roll mode and did not make the turn to deeer. The FMS did sequence to deeer though and we were able to engage LNAV mode again and remain on course. On the ground; I tried inputting the flight plan again into the FMS and verified that when you make a runway change with the SPIDR1 arrival loaded; it causes the spidr waypoint to appear twice.contact honeywell to see if there is an error in the database or software.
Original NASA ASRS Text
Title: EMB-145 Captain reported an anomaly with his Honeywell FMS. When changing runway assignment on arrival to RIC the FMS loaded the waypoint SPIDR twice.
Narrative: We were originally cleared to Richmond via flight planned routing to the MOL transition of the SPIDR1 arrival. The Honeywell FMS doesn't allow you to load the SPIDR1 arrival until you've chosen a landing runway; so while I was loading the FMS prior to departure I selected runway 20 and verified the fixes were correct with the chart. While flying the arrival just prior to REDNG; we contacted Potomac Approach and they assigned runway 16 so I changed the runway in the FMS to match. Our jumpseater noticed that after I did this the flight plan in the FMS showed SPIDR twice between HEMME and DEEER. Also; when we crossed over SPIDR the flight guidance went in to roll mode and did not make the turn to DEEER. The FMS did sequence to DEEER though and we were able to engage LNAV mode again and remain on course. On the ground; I tried inputting the flight plan again into the FMS and verified that when you make a runway change with the SPIDR1 arrival loaded; it causes the SPIDR waypoint to appear twice.Contact Honeywell to see if there is an error in the database or software.
Data retrieved from NASA's ASRS site 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.