Porter flight cancelled after child refuses seatbelt, leaving passengers stranded overnight in Victoria
VICTORIA, B.C. — A Porter Airlines flight from Victoria to Toronto was cancelled late Thursday night after a young child refused to remain seated and secure a seatbelt, forcing the aircraft to return to the terminal and ultimately causing the flight to miss Victoria International Airport’s overnight operating window.
Porter Airlines flight PD444 was scheduled to depart Victoria International Airport for Toronto Pearson International Airport on August 6. The aircraft had already pushed back from the gate and was taxiing for departure when cabin crew discovered that a young child was standing on their seat and would not remain secured.
Porter said the child’s parent and members of the cabin crew attempted to resolve the situation.
The airline said the aircraft could not depart while the child remained unsecured and the crew therefore returned to the terminal.
What followed turned a passenger safety issue into a disruption affecting the entire flight.
According to Porter, returning the aircraft to the terminal required the aircraft to be reconnected to the terminal, the affected passengers to disembark, their checked baggage to be retrieved and the flight plan and other required paperwork to be completed.
By the time those procedures were completed, the aircraft could no longer depart before Victoria International Airport’s scheduled 12:30 a.m. airfield closure.
The flight was cancelled and the remaining passengers were required to travel the following day.
Porter apologized for the disruption and said the affected passengers were able to depart on a flight the following day.
Passengers faced an unexpected overnight delay
The cancellation meant passengers who had boarded an overnight flight to Toronto instead faced an unplanned stay in Victoria.
Passenger accounts published online indicate that travellers were rebooked for the following day, while some passengers were left seeking information about accommodation and other arrangements following the cancellation.
One passenger who identified themselves as having been aboard the flight described difficulties communicating with the airline after the cancellation and said passengers had to make arrangements for the night.
Other passenger accounts have raised questions about whether hotel accommodation, meals and transportation were provided or reimbursed by Porter.
Those individual accounts have not established how the airline handled every passenger’s expenses.
What did Porter provide?
The overnight cancellation has raised questions about the assistance available to passengers following the disruption.
Skeena News sought clarification from the relevant authorities regarding the cancellation, passenger assistance, accommodation, reimbursement and the circumstances surrounding the missed 12:30 a.m. operating window.
As of August 10, Skeena News had not received answers to those questions.
It remains unclear from the information publicly available:
- how many passengers were aboard PD444;
- exactly how much time elapsed between the aircraft’s return to the gate and the airport’s 12:30 a.m. closure;
- what accommodation was offered to passengers;
- how many passengers required hotel accommodation;
- whether hotel, meal or transportation expenses were paid directly or reimbursed;
- whether any passengers purchased alternative flights;
- the total financial cost of the cancellation to Porter; and
- whether Porter requested or considered an exception to the airport’s operating restrictions.
Passenger compensation remains a separate question
The incident also raises questions under Canada’s Air Passenger Protection Regulations.
Whether passengers are entitled to compensation depends on the circumstances of the disruption and how it is classified under the applicable passenger-protection rules.
The initial incident involved a passenger who could not be safely secured. Porter has said that the aircraft was unable to depart in that condition and that returning to the terminal was necessary.
However, the cancellation occurred only after the aircraft missed the airport’s 12:30 a.m. operating window.
That distinction is significant because passenger entitlements can depend on whether a disruption is considered within an airline’s control, required for safety, or outside the airline’s control.
Porter has not publicly provided a detailed explanation of how it has classified the cancellation for passenger-protection purposes.
As a result, it would be premature to state that passengers were automatically entitled to a particular amount of cash compensation.
The critical period before the airport closure
The circumstances surrounding the period between the aircraft’s return to the terminal and the airport’s 12:30 a.m. closure remain one of the key unanswered aspects of the incident.
Porter said the aircraft had to be reconnected to the terminal, the affected passengers had to be removed, their baggage retrieved and flight plans and other paperwork completed.
Those procedures ultimately consumed enough time for the aircraft to miss the departure window.
The decision to prevent an unsecured passenger from travelling was a safety matter. The more complicated operational question is whether the subsequent process could have been completed quickly enough for the aircraft to depart before the airport closed.
Public passenger accounts provide different details about the timing of the aircraft’s return to the gate, but those accounts have not been independently verified.
Without detailed operational records from Porter or the airport, it is not possible to establish from publicly available information exactly how each minute was accounted for.
A disruption that affected an entire aircraft
The incident illustrates how a relatively isolated passenger safety problem can develop into a major operational disruption when it occurs late at night at an airport with a fixed operating window.
The sequence was straightforward but consequential: a child could not be secured; the aircraft returned to the terminal; the affected passengers and baggage were removed; additional operational procedures were required; the aircraft missed the airport’s 12:30 a.m. closure; and the entire flight was cancelled.
The passengers who had expected to arrive in Toronto the following morning instead faced a delay extending into the next day.
The recovery flight eventually departed Victoria on August 7.
What remains unanswered
The public information currently available establishes the reason for the initial return to the terminal and the fact that the aircraft subsequently missed the airport’s operating window.
It does not establish the full operational timeline, the number of passengers affected, the assistance provided to each passenger or the final financial cost of the cancellation.
Skeena News contacted the relevant authorities seeking answers to those questions. No answers had been received by August 10.
For the passengers aboard PD444, what began as a safety issue involving one passenger ultimately resulted in the cancellation of the entire flight and an unexpected overnight disruption for everyone on board.
