The Federal Board of Revenue (FBR) has once again frozen the accounts of the Pakistan International Airlines (PIA) over non-payment of dues, which has disturbed the schedule of the national flag carrier’s flights.
The PIA spokesperson confirmed the move, saying contacts with the FBR at the government level continued for the restoration of accounts.
He said despite the closure of accounts, the airline continued its flight operations.
The national flag carrier owes more than Rs2 billion on account of taxes for the past several months to the government.
The airline’s 53 accounts were frozen last year also over non-payment of dues, which were later restored on assurance of early payments.
Meanwhile, according to the sources, the PSO refused to supply fuel to the PIA following which the schedule of its three flights was disturbed.
The flights whose operations were affected include PK309 from Islamabad to Karachi, PK330 from Karachi to Multan and PK739 from Multan to Jeddah.
Meanwhile, The Pakistan International Airline (PIA) has published a tender notice for hiring services of a “well-reputed” cargo handling agent for handling its flights in Paris, raising hopes about the return of the national flag carrier to the European Union (EU).
Such cargo handling agents may get details about submission of proposals and scope of work at the PIA and the Pakistan Procurement Regulatory Authority (PPRA) websites. The proposal can be submitted to the PIA country manager for France by August 24, when the bids will be opened.
According to sources, the PIA administration has started making preparations to restart its flight operations at different destinations of the EU, beginning with France.
The European Union Aviation Safety Agency (EASA) on January 22 refused to lift a ban imposed on the PIA to travel to European countries and the United Kingdom after an online audit conducted by the International Civil Aviation Organisation (ICAO).
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ