 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier captain notes that fix names are different on the boi runway 28L localizer back course commercial chart approach plate and his FMC.
| Attributes | |
| ACN | 729644 |
| Time | |
| Date | 200702 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : boi.airport |
| State Reference | ID |
| Altitude | msl single value : 5900 |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tower : boi.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | ils localizer only : 28l other |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument non precision |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 150 flight time type : 150 |
| ASRS Report | 729644 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Aircraft Chart Or Publication FAA |
| Primary Problem | Ambiguous |
| Situations | |
| Chart | approach : boi rwy 28l loc/bc |
Narrative:
The fixes for the localizer back course runway 28L at boi do not correlate with the fixes in the FMC when you program it for the same approach. Specifically; D9.1 comes up as CF11 and D5.1 comes up as FF11 (or something like that). The safety issue with this approach; in my opinion; is that all the fixes on commercial chart should correlate exactly with the fixes in the FMC. You can eventually figure out what is what; but in these cases where you have to fly the localizer back course; I prefer to do it in LNAV and then switch out. In this case; it's not as easy as it should be and I found myself flipping the navigation switch up and down to maintain navigation sa. The localizer back course runway 34L in rno (which we had to fly right after this one) had all the points correlate. Can't the folks at boi/terps come up with better names for those fixes so all the information correlates?
Original NASA ASRS Text
Title: ACR CAPT NOTES THAT FIX NAMES ARE DIFFERENT ON THE BOI RWY 28L LOC BC COMMERCIAL CHART APCH PLATE AND HIS FMC.
Narrative: THE FIXES FOR THE LOC BC RWY 28L AT BOI DO NOT CORRELATE WITH THE FIXES IN THE FMC WHEN YOU PROGRAM IT FOR THE SAME APCH. SPECIFICALLY; D9.1 COMES UP AS CF11 AND D5.1 COMES UP AS FF11 (OR SOMETHING LIKE THAT). THE SAFETY ISSUE WITH THIS APCH; IN MY OPINION; IS THAT ALL THE FIXES ON COMMERCIAL CHART SHOULD CORRELATE EXACTLY WITH THE FIXES IN THE FMC. YOU CAN EVENTUALLY FIGURE OUT WHAT IS WHAT; BUT IN THESE CASES WHERE YOU HAVE TO FLY THE LOC BC; I PREFER TO DO IT IN LNAV AND THEN SWITCH OUT. IN THIS CASE; IT'S NOT AS EASY AS IT SHOULD BE AND I FOUND MYSELF FLIPPING THE NAV SWITCH UP AND DOWN TO MAINTAIN NAV SA. THE LOC BC RWY 34L IN RNO (WHICH WE HAD TO FLY RIGHT AFTER THIS ONE) HAD ALL THE POINTS CORRELATE. CAN'T THE FOLKS AT BOI/TERPS COME UP WITH BETTER NAMES FOR THOSE FIXES SO ALL THE INFORMATION CORRELATES?
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.