 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B767-200 pilot advises aircraft database does not include VOR ILS runway 10 at ttpp.
| Attributes | |
| ACN | 764611 |
| Time | |
| Date | 200712 |
| Place | |
| Locale Reference | airport : ttpp.airport |
| State Reference | FO |
| Aircraft 1 | |
| Flight Phase | ground : maintenance |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| ASRS Report | 764611 |
| Events | |
| Anomaly | non adherence : published procedure |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : unable none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Aircraft Company |
| Primary Problem | Aircraft |
Narrative:
There is a potential human factors problem with the ILS runway 10 approach to ttpp. Typically we are cleared to shark intersection followed by the VOR ILS runway 10 approach. The problem is; the only ILS approach in the FMS database is the NDB ILS runway 10. The approachs are similar except for the missed approach. One takes you west to the tri NDB; and the other takes you south to the position VOR. The problem would be a pilot flying the FMS missed approach to the tri NDB when ATC is expecting the pilot to navigation to the position VOR in a non-radar environment. I suggest we add the VOR ILS runway 10 approach to the FMS database. If that is not possible; correctly code the existing ILS approach in the FMS database as NDB ILS runway 10 and put a note on the chart page pointing out the difference. It has been my observation; most pilots are not aware of this discrepancy.
Original NASA ASRS Text
Title: B767-200 PLT ADVISES ACFT DATABASE DOES NOT INCLUDE VOR ILS RWY 10 AT TTPP.
Narrative: THERE IS A POTENTIAL HUMAN FACTORS PROB WITH THE ILS RWY 10 APCH TO TTPP. TYPICALLY WE ARE CLRED TO SHARK INTXN FOLLOWED BY THE VOR ILS RWY 10 APCH. THE PROB IS; THE ONLY ILS APCH IN THE FMS DATABASE IS THE NDB ILS RWY 10. THE APCHS ARE SIMILAR EXCEPT FOR THE MISSED APCH. ONE TAKES YOU W TO THE TRI NDB; AND THE OTHER TAKES YOU S TO THE POS VOR. THE PROB WOULD BE A PLT FLYING THE FMS MISSED APCH TO THE TRI NDB WHEN ATC IS EXPECTING THE PLT TO NAV TO THE POS VOR IN A NON-RADAR ENVIRONMENT. I SUGGEST WE ADD THE VOR ILS RWY 10 APCH TO THE FMS DATABASE. IF THAT IS NOT POSSIBLE; CORRECTLY CODE THE EXISTING ILS APCH IN THE FMS DATABASE AS NDB ILS RWY 10 AND PUT A NOTE ON THE CHART PAGE POINTING OUT THE DIFFERENCE. IT HAS BEEN MY OBSERVATION; MOST PLTS ARE NOT AWARE OF THIS DISCREPANCY.
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.