37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1280918 |
Time | |
Date | 201507 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | EMB ERJ 170/175 ER/LR |
Operating Under FAR Part | Part 121 |
Flight Phase | Parked |
Component | |
Aircraft Component | Electronic Flt Bag (EFB) |
Person 1 | |
Function | Dispatcher |
Qualification | Dispatch Dispatcher |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Procedural FAR |
Narrative:
Shortly after sending the release; I was notified by the first officer (first officer) that his efb (electronic flight bag) (ipad) was not working and mentioned that he would need charts emailed to him to be able to operate the flight. The charts were sent and I asked the coordinator to verify that was all that was needed to be done which he agreed.all parties who were involved in this overlooked the [operations manual] and misinterpreted that the flight could still operate with the efb inop as long as the first officer had the required charts. With the first officer saying he just needed charts and the coordinators telling me that was all that would be required; I did not look up and confirm with the bulletin myself that it was indeed the actual procedure. Going back and reviewing the bulletin; the only way the flight should of operated as a revenue flight was if...the pilot may use a deadheading/commuting flight crewmember's efb.the pilot may be replaced with a reserve.with this being a fairly recent change; we were confusing the efb mount inop (charts required for revenue flight) procedure with what steps should've been taken if the actual efb failed itself (cannot operate as revenue).
Original NASA ASRS Text
Title: First Officer reports his EFB (Electronic Flight Bag) failed and requested the applicable trip charts to be emailed. His Dispatcher reported he later determined either an EFB should have been borrowed or the pilot replaced. An EFB is required.
Narrative: Shortly after sending the release; I was notified by the FO (First Officer) that his EFB (Electronic Flight Bag) (IPAD) was not working and mentioned that he would need charts emailed to him to be able to operate the flight. The charts were sent and I asked the coordinator to verify that was all that was needed to be done which he agreed.All parties who were involved in this overlooked the [operations manual] and misinterpreted that the flight could still operate with the EFB inop as long as the FO had the required charts. With the FO saying he just needed charts and the coordinators telling me that was all that would be required; I did not look up and confirm with the bulletin myself that it was indeed the actual procedure. Going back and reviewing the bulletin; the only way the flight should of operated as a revenue flight was if...The Pilot may use a deadheading/commuting Flight Crewmember's EFB.The Pilot may be replaced with a reserve.With this being a fairly recent change; we were confusing the EFB mount inop (charts required for revenue flight) procedure with what steps should've been taken if the actual EFB failed itself (cannot operate as revenue).
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.