B737 CREW DEPARTED ON THE FLT WITH PAX WHEN SCHEDULED AS A FERRY FLT.
Synopsis
B737 CREW DEPARTED ON THE FLT WITH PAX WHEN SCHEDULED AS A FERRY FLT.
Narrative
AT APPROX XA23; FLT XXXX LEFT MCI ON ITS WAY TO MHT. THE EARLIER REVENUE FLT TO DCA HAD BEEN CANCELED AND THE FERRY FLT XXXX HAD BEEN CREATED TO FERRY THE FLT TO MHT TO PICK UP PAX. ACR X LOAD CTL WAS AWARE OF THE FERRY FLT AND PLANNED ACCORDINGLY. NO PROVISIONS WERE MADE OR PLANNED FOR PAX TO BE ON THIS FLT. AT APPROX XA45 I WAS INFORMED BY OUR AIRLINE COORDINATOR THAT FLT XXXX HAD TAXIED AWAY FROM THE GATE WITH REVENUE PAX ON BOARD. I CALLED THE STATION AND CONTACTED THE ACFT VIA ACARS TO INFORM THEM THAT THEY NEEDED TO COME BACK TO THE GATE. THE REASON WAS SO THAT WE COULD EITHER RECLASSIFY THE FLT AS A REVENUE FLT OR TAKE THE PAX OFF TO COMPLY WITH OUR OPERATIONAL PROCS CONCERNING FLT NUMBERS. WHEN I GOT THROUGH TO MCI OPS; I WAS TOLD BY OPS THAT THE FLT HAD ALREADY LEFT THE GND HEADED FOR MHT WITH REVENUE PAX ON BOARD. I CONTACTED CENTRAL LOAD CTL AND THEY INFORMED ME THAT THEY HAD MADE NO PROVISIONS FOR PAX AND THAT IT WAS INDEED A NON REVENUE FERRY FLT. I REQUESTED A SECOND SERIES OF WT AND BAL FIGURES TO ACCOUNT FOR THE PAX ON BOARD. A NEW WT AND BAL SERIES FOUND THAT THE ACFT WAS WELL WITHIN ITS OPERATIONAL LIMITS. I INFORMED THE CAPT OF THE FLT THAT I WOULD BE FILING A RPT ON THE IRREGULARITY AND THAT IT WAS UNDERSTOOD THAT HE WOULD BE PROCEEDING TO MHT AND TO CONTACT ME UPON HIS ARR. NO EMER WAS DECLARED AND NO PAX WERE INJURED DURING THIS EVENT.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.