 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 flight crew reported that they were unable to get the performance weight and balance landing data through ACARS.
| Attributes | |
| ACN | 1492422 |
| Time | |
| Date | 201710 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.ARTCC |
| State Reference | US |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Data Transmission and Automatic Calling |
| Person 1 | |
| Function | Pilot Flying Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Pilot Not Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Speed All Types Inflight Event / Encounter Unstabilized Approach |
Narrative:
On the short flight we briefed in depth the [approach] page and the possibility of different taxi routes. This caused us to be late on getting the performance weight and balance landing performance. As we continued on the arrival; we decided to use the aerodata app to get the data. I transferred control to the first officer (first officer) to work on getting data. After not being able to get the data I notified ATC that we needed delayed vectors to contact our dispatch to receive our data. ATC continued to push us into the approach not really caring that we asked for delayed vectors. I let them know again.they slowed us to 180 knots and I noticed that we were still clean at 180 knots so we selected flaps 5. I monitored number 2 radio and finally got dispatch and landing on about a 15 mile final. After landing and exiting the runway the ACARS chimes and our landing data came through. We called maintenance and they reset the ACARS to clear the memory of the system. This distraction caused us to be in the yellow which caused us to be clean at 180 knots. I should have been more assertive with ATC and not let them push us into the approach.
Original NASA ASRS Text
Title: B737 flight crew reported that they were unable to get the performance weight and balance landing data through ACARS.
Narrative: On the short flight we briefed in depth the [approach] page and the possibility of different taxi routes. This caused us to be late on getting the performance weight and balance landing performance. As we continued on the arrival; we decided to use the AeroData app to get the data. I transferred control to the First Officer (FO) to work on getting data. After not being able to get the data I notified ATC that we needed delayed vectors to contact our Dispatch to receive our data. ATC continued to push us into the approach not really caring that we asked for delayed vectors. I let them know again.They slowed us to 180 knots and I noticed that we were still clean at 180 knots so we selected flaps 5. I monitored number 2 radio and finally got dispatch and landing on about a 15 mile final. After landing and exiting the runway the ACARS chimes and our landing data came through. We called Maintenance and they reset the ACARS to clear the memory of the system. This distraction caused us to be in the Yellow which caused us to be clean at 180 knots. I should have been more assertive with ATC and not let them push us into the approach.
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.