37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1651495 |
Time | |
Date | 201906 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | AVP.Airport |
State Reference | PA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 900 (CRJ900) |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Commercial Flight Crew Private Flight Crew Multiengine Flight Crew Instrument |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
The dispatcher had accidentally selected improper toggle switches on computer creating a dispatch release without valid landing data on the release. The dispatcher had selected inoperative nose wheel steering and contaminated runway conditions; both of which did not exist. During the enroute phase; I attempted to acquire landing data for our arrival and received an error message on ACARS indicating that no landing data could be created due to nose wheel steering inop on with a contaminated runway. We were confused because the nose wheel steering was not inop and the runway was not contaminated. The captain contacted dispatch via ACARS and received an amended release with the improper toggles removed. We received the proper landing data and landed without incident. The captain talked to the dispatcher on the ground at the gate and the dispatcher advised filing an as soon as possible. In the future I will be diligent to back up the captain by reviewing all aspects of the release even when I am the pilot monitoring for the flight.
Original NASA ASRS Text
Title: CRJ-900 First Officer reported inaccurate landing data was received from Dispatch.
Narrative: The Dispatcher had accidentally selected improper toggle switches on computer creating a Dispatch Release without valid landing data on the release. The Dispatcher had selected inoperative nose wheel steering and contaminated runway conditions; both of which did not exist. During the enroute phase; I attempted to acquire landing data for our arrival and received an error message on ACARS indicating that no landing data could be created due to nose wheel steering inop on with a contaminated runway. We were confused because the nose wheel steering was not inop and the runway was not contaminated. The Captain contacted Dispatch via ACARS and received an amended release with the improper toggles removed. We received the proper landing data and landed without incident. The Captain talked to the Dispatcher on the ground at the gate and the Dispatcher advised filing an ASAP. In the future I will be diligent to back up the Captain by reviewing all aspects of the release even when I am the Pilot Monitoring for the flight.
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.