 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737 first officer reported his captain was unaware of a special procedure that was not being displayed on their ipads.
| Attributes | |
| ACN | 1294984 |
| Time | |
| Date | 201509 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | SFO.Airport |
| State Reference | CA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Tablet |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 173 Flight Crew Total 8034 Flight Crew Type 2684 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
Although no sops were violated; there appears to be a systematic threat for all pilots.during the preflight setup I gathered the plan data for a 1R departure in sfo. I circled the max thrust data and set the V2 speed. During the preflight briefing the captain asked why I had chosen max thrust and told him it was to comply with the operations alert for 737s requiring max thrust takeoffs and flaps 5 or greater. He commented that he had just reviewed the ops alerts in the mobile app for this leg and that alert was not listed. I looked at my app and saw that the alert was not listed in mine either. I showed him the ops alert at which point we agreed to continue with the briefing and flight using max thrust. Sops were followed. The threat to this flight was since the captain had not flown much recently; he used the mobile app to refresh his memory about current operations alerts but this one was missing and so he was not prepared to comply with it.
Original NASA ASRS Text
Title: B737 First Officer reported his Captain was unaware of a special procedure that was not being displayed on their iPads.
Narrative: Although no SOPs were violated; there appears to be a systematic threat for all pilots.During the preflight setup I gathered the plan data for a 1R departure in SFO. I circled the max thrust data and set the V2 speed. During the preflight briefing the Captain asked why I had chosen max thrust and told him it was to comply with the OPS Alert for 737s requiring max thrust takeoffs and flaps 5 or greater. He commented that he had just reviewed the Ops Alerts in the Mobile App for this leg and that Alert was not listed. I looked at my app and saw that the alert was not listed in mine either. I showed him the Ops Alert at which point we agreed to continue with the briefing and flight using max thrust. SOPs were followed. The threat to this flight was since the Captain had not flown much recently; he used the Mobile app to refresh his memory about current OPS Alerts but this one was missing and so he was not prepared to comply with it.
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.