37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 863613 |
Time | |
Date | 200912 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | DCA.Airport |
State Reference | DC |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
In october during my rnp qualification with the company check airman and the air carrier's B737 FAA representative in attendance; a discussion on the dca approaches (because training is using the RNAV (rnp) runway 19 approach in the simulator) occurred about the fact that our B737 FMS database does not contain the rosslyn lda runway 19 approach. The lda runway 19 is in the database and has lower minimum than does the rosslyn lda. However; having flown extensively out of dca; the rosslyn lda is the weapon of choice used by washington ATC to get aircraft landing runway 19 under a higher overcast to essentially finish the approach as a visual using the potomac river. The FAA representative stated that due to our non-ILS approach procedures; this approach is considered a raw data approach and as such; should be referred to the QRH and briefed as an abnormal procedure. He also recommended that all crews should then file a report about the approach. I have seen a several year old circular briefings addressing this situation and not explaining how the FMS has a problem entering 2 approaches with the same runway designation. The database manufacturer and our air carrier were; however; going to fix this situation by giving letter designations to each approach such as the lda Y runway 19 (rosslyn) and the lda Z runway 19 (lda runway 19). Since I have not seen any further response concerning the above situation and with the winter months setting in; I felt in accordance with or FAA representative's instructions concerning the fleet wide report recommendations; this message needs to get out to the crews until the company; the database manufacturer; and the FAA can review this situation.
Original NASA ASRS Text
Title: A B737NG Captain reports that the aircraft's FMC database displays only the DCA RNAV (RNP) 19; and is currently unable to present both the DCA ROSSLYN LDA and DCA RNAV (RNP) 19.
Narrative: In October during my RNP qualification with the Company Check Airman and the Air Carrier's B737 FAA representative in attendance; a discussion on the DCA approaches (because training is using the RNAV (RNP) Runway 19 approach in the simulator) occurred about the fact that our B737 FMS database does not contain the Rosslyn LDA Runway 19 approach. The LDA Runway 19 is in the database and has lower minimum than does the Rosslyn LDA. However; having flown extensively out of DCA; the Rosslyn LDA is the weapon of choice used by Washington ATC to get aircraft landing Runway 19 under a higher overcast to essentially finish the approach as a visual using the Potomac River. The FAA Representative stated that due to our Non-ILS Approach procedures; this approach is considered a raw data approach and as such; should be referred to the QRH and briefed as an abnormal procedure. He also recommended that all crews should then file a report about the approach. I have seen a several year old circular briefings addressing this situation and not explaining how the FMS has a problem entering 2 approaches with the same Runway designation. The database manufacturer and our Air Carrier were; however; going to fix this situation by giving letter designations to each approach such as the LDA Y Runway 19 (Rosslyn) and the LDA Z Runway 19 (LDA Runway 19). Since I have not seen any further response concerning the above situation and with the winter months setting in; I felt in accordance with or FAA representative's instructions concerning the fleet wide report recommendations; this message needs to get out to the crews until the company; the database manufacturer; and the FAA can review this situation.
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.