 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A320 captain and the associated dispatcher reported that the aircraft was flown on schedule with passengers when it was listed as out of service.
| Attributes | |
| ACN | 1473709 |
| Time | |
| Date | 201708 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Light | Dawn |
| Aircraft 1 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Dispatcher |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural FAR Deviation - Procedural Maintenance Deviation - Procedural Published Material / Policy |
Narrative:
It was a normal morning. Inspected the cockpit and log book and found nothing out of the ordinary. I did the walk around and everything was in its place. The logbook had a sign off from the night before of a periodic inspection and the aircraft was signed back into service. So we boarded up and took off. When we were a little over an hour into the flight we got contacted by dispatch saying we were on maintenance and we were not supposed to leave. The dispatcher said he had 'blown out' our performance data so it wouldn't come up for takeoff. Yet I ran the data 8 min prior to departure and it came back fine. We were not informed by dispatch; maintenance; [operations]; the station; or anyone else of any delay. The red 'do not operate' tag was not on the thrust levers and no entry was in the logbook indicating any maintenance was necessary. There was literally no way we as a crew could know anything was going on until after dispatch contacted us. At which point we continued on to [the destination] with no issues. Someone from the company or station needs to be aware of the mx event and inform the crew. The red out of service tag should be used and an entry made in the logbook of a maintenance event that is currently happening. That way a crew showing up knows there is maintenance.
Original NASA ASRS Text
Title: A320 Captain and the associated Dispatcher reported that the aircraft was flown on schedule with passengers when it was listed as out of service.
Narrative: It was a normal morning. Inspected the cockpit and log book and found nothing out of the ordinary. I did the walk around and everything was in its place. The logbook had a sign off from the night before of a periodic inspection and the aircraft was signed back into service. So we boarded up and took off. When we were a little over an hour into the flight we got contacted by dispatch saying we were on maintenance and we were not supposed to leave. The dispatcher said he had 'blown out' our performance data so it wouldn't come up for Takeoff. Yet I ran the data 8 min prior to departure and it came back fine. We were not informed by dispatch; maintenance; [Operations]; the station; or anyone else of any delay. The red 'Do not operate' tag was not on the thrust levers and no entry was in the logbook indicating any maintenance was necessary. There was literally no way we as a crew could know anything was going on until after dispatch contacted us. At which point we continued on to [the destination] with no issues. Someone from the company or station needs to be aware of the mx event and inform the crew. The red out of service tag should be used and an entry made in the logbook of a maintenance event that is currently happening. That way a crew showing up knows there is maintenance.
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.