![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1512554 |
| Time | |
| Date | 201801 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Regional Jet 700 ER/LR (CRJ700) |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Pilot Not Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
Near top of descent; I listened to the ASOS to get the current wx. The ASOS noted clear skies and no precipitation; but there was a NOTAM for dry snow on all surfaces. I then ran the data for landing including 'dry snow' for the landing performance. The [landing data system] returned information for 'wet snow' and suggested using thrust reverser credit. I verified that I had entered 'dry snow;' which I had. Just to see what would happen; I reentered data for 'wet snow' and the [landing data system] returned data for a normal dry runway. I knew this was really odd; and was probably an it issue of some kind. This could be dangerous; as we did not have enough distance to land on 'wet snow;' with no TR (thrust reverser) credit; but if 'wet snow' were entered; it would give erroneous dry runway numbers; making the crew think there was enough distance when there wasn't. I then decided to enter 'dry snow' with thrust reverser credit; and the [landing data system] with 'wet snow' and TR credit returned numbers that allowed us to land; which was more conservative than 'dry snow' with TR credit.this must be some kind of it issue that needs to be looked in to. Returning [landing data] with parameters different than what was entered should not occur.
Original NASA ASRS Text
Title: CRJ-700 Captain reported receiving inaccurate runway data from the landing data system.
Narrative: Near top of descent; I listened to the ASOS to get the current wx. The ASOS noted clear skies and no precipitation; but there was a NOTAM for dry snow on all surfaces. I then ran the data for landing including 'dry snow' for the landing performance. The [landing data system] returned information for 'wet snow' and suggested using thrust reverser credit. I verified that I had entered 'dry snow;' which I had. Just to see what would happen; I reentered data for 'wet snow' and the [landing data system] returned data for a normal dry runway. I knew this was really odd; and was probably an IT issue of some kind. This could be dangerous; as we did not have enough distance to land on 'wet snow;' with no TR (Thrust Reverser) credit; but if 'wet snow' were entered; it would give erroneous dry runway numbers; making the crew think there was enough distance when there wasn't. I then decided to enter 'dry snow' with thrust reverser credit; and the [landing data system] with 'wet snow' and TR credit returned numbers that allowed us to land; which was more conservative than 'dry snow' with TR credit.This must be some kind of IT issue that needs to be looked in to. Returning [landing data] with parameters different than what was entered should not occur.
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.