<?xml version="1.0" encoding="UTF-8"?>                                                                                                                                         <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> <channel> <title>Finnair news</title> <description> Finnair news RSS </description> <link> https://www.finnair.com/int/gb/information-services/flights/news </link> <atom:link href="https://www.finnair.com:443/pl/AYPortal/wds/DisplayPage.action?SITE=FINRFINR&amp;COUNTRY_SITE=INT&amp;PAGE=NRSS&amp;LANGUAGE=GB&amp;FORMAT=rss&amp;ENTITY=news" rel="self" type="application/rss+xml" />   <item> <title>  Changes to booking a bicycle on Finnair operated and marketed flights </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_changes-to-booking-a-bicycle-on-finnair-operated-and-marketed-flights </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 05.12.2019 - Changes to booking a bicycle on Finnair operated and marketed flights </td> </tr> <tr> <td> <p>There are changes to <strong class="amp">booking a bicycle on Finnair operated and marketed flights as of 3.12.2019</strong>: When you book a bicycle for a customer on Finnair marketed and operated flights, the system will <strong class="amp">automatically check whether there is quota available for the specific flight and aircraft type and confirm the SSR if there is quota available</strong>. The maximum quota for BIKE cannot be exceeded due to restrictions in cargo hold space. The requirements to get an auto-confirmation:</p>
<ul>
    <li>Customer has a Finnair operated and marketed flight</li>
    <li>There is quota available for the specific flight(s)</li>
    <li>The BIKE SSR is added in a correct format to the PNR, example: SR BIKE AY NN1-BIKE DIMS 150X30X50CMS 15KGS</li>
</ul>
<p>Please note! If the customer has connecting flights with other airlines, the SSR is not automatically confirmed and the operating carrier of the connecting flight needs to be contacted separately to confirm bicycle on their flight segments.</p> </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_changes-to-booking-a-bicycle-on-finnair-operated-and-marketed-flights </guid> <pubDate> Thu, 5 Dec 2019 00:00:00 +0000 </pubDate> </item>   <item> <title>  Finnair will be introducing a new Ticketing Time Limit notification format </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_Ticketing Time Limit </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 02.12.2019 - Finnair will be introducing a new Ticketing Time Limit notification format </td> </tr> <tr> <td> <p>Please be advised that the current
SSR OTHS messages for ticketing time limits in individual PNRs will be replaced
by OPW and OPC elements <i>(for Amadeus
agents)</i> and SSR ADTK <i>(for non-Amadeus
agents)</i> starting December 9, 2019 <i>(this
applies for PNRs created from this day onwards and PNRs created prior to this
date but modified on this day or later)</i>. This allows Finnair to accurately calculate
and apply ticketing time limits and notify agents in real-time. </p>

<p><br></p>

<p>Travel agencies benefit from this
by receiving reliable information about ticketing time limits at booking time
and can provide accurate ticketing time limit to the customer instantly. In
case of rebooking a new time limit will be updated to the PNR.</p>

<p><br></p>

<p>Current SSR OTHS is added to a PNR
with up to 4 hours’ delay from EOT/booking creation and only then queued to
booking office for attention. The new OPC element <i>(for Amadeus agents)</i> and SSR ADTK <i>(for non-Amadeus agents) </i>will be processed immediately after EOT/booking
creation and queued to booking office for attention.</p>

<p><br></p>

<p>In case ticket is not issued before
the time limit expiry, segments are cancelled and PNR is queued to booking
office for attention.</p>

<p><br></p>

<p><br></p>

<p>For Amadeus agents, there are two
elements in the new procedure:</p>

<ul><li>OPW –
warning for time limit to remind about the approaching ticketing time <i>limit (used only when the fare booked
carries a flexible time limit)</i></li><li>OPC –
cancellation time limit or last day to issue ticket. If no ticket issued before
the given date and time, unticketed segments will be cancelled</li></ul>



<p><br></p>

<p>For all other GDS users, the time
limit will be shown as:</p>

<ul><li>SSR
ADTK element</li></ul>

<p><br></p>

<p><b>&nbsp;</b></p>

<p><b>During the transition to the new
Time Limit Notification format </b>SSR
OTHS and OPC/SSR ADTK could be visible in a PNR in different lines. Only OPC/SSR
ADTK will be the value to consider for the ticketing time limit deadline. <b></b></p>

<p><br></p>

<p>Both OPW and OPC are segment
associated. If a ticket is issued, the OPW / OPC elements are removed from the
booking.</p>

<p><br></p>

<p><b>Please
note</b> – All unticketed PNRs
created prior to December 9, 2019 which have not been modified on December 9
nor December 10, will be processed for the new Time Limit Notification format on
December 11, 2019. On this day, all unticketed PNRs will be queued to booking
office for attention. Travel agent partners are asked to review the PNRs and
acknowledge the new time limit and Time Limit format in each PNR. Please note
that in some cases the new time limit might differ from the time limit in the
old format.</p>

<p><br></p>

<p>Example of the elements:</p>

<ul><li>An OPW
element will be created after EOT to notify accurate TTL</li></ul>

<p><b>OPW</b>-31DEC:1435/1C7/AY
REQUIRES TICKET ON OR BEFORE 03JAN:1435 HEL TIME ZONE/TKT/S3-4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ​</p>

<ul><li>An OPC
element will process cancellation when the ticketing time limit is reached and if
no ticket is issued</li></ul>

<p><b>OPC</b>-03JAN:1435/1C8/AY
CANCELLATION DUE TO NO TICKET HEL TIME ZONE​/TKT/S3-4/P1-2&nbsp; </p>

<p><br></p>

<p><br></p>

<p>All other GDS users will be
notified about the ticketing time limits as SSR ADTK element: </p>

<p>SSR ADTK ZZ TO AY BY 11JAN 1759 HEL
TIME ZONE OTHERWISE WILL BE XLD </p>

<p>(ZZ = indicator for the GDS through
which the booking was created)</p> </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_Ticketing Time Limit </guid> <pubDate> Mon, 2 Dec 2019 00:00:00 +0000 </pubDate> </item>   <item> <title>  Distribution in Sabre and Abacus stopped </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_dist_sabre_abacus_stopped </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 26.11.2019 - Distribution in Sabre and Abacus stopped </td> </tr> <tr> <td> <p>Finnair content has been fully removed from Sabre and Abacus GDSs as of Tuesday 26th November. The distribution agreement has not been reached with Sabre and Abacus GDS.</p>
<p>Finnair has been negotiating with Sabre, one of the largest Global Distribution Systems (GDS) based in the US, on an agreement to replace the current Full Content Agreement (FCA) and to allow moving to our desired state of pricing and distribution freedom in direct channels and content differentiation in indirect channels. As we have not yet reached an agreement, Sabre has removed Finnair content (flight inventory, flight prices etc.) from Sabre and Abacus GDSs as of Tuesday 26th November, excluding the European markets for now. Apart from the exclusion markets this means that travel agents cannot book anymore Finnair flights or ancillary products from Sabre or Abacus GDSs.</p>
<p>We are sorry about the inconvenience this is causing to travel agents and are working to find a solution with Sabre. Meanwhile, Finnair continues to distribute via all the other GDSs e.g. Amadeus, Travelport, Travelsky. Also, Finnair content is available via selected aggregator platforms such as Travelfusion and PKfare and via direct NDC connections. 
</p><br>

<p><strong>Instructions for active reservations in Sabre and Abacus GDSs</strong></p><br>

<p><strong>Ticketed PNRs</strong></p><br>

<p>Current fare rules (including penalties & refunds) apply.<br>

Changes and other amendments including cancellations should be done via Finnair Contact Centers or via Manage Booking at finnair.com</p><br>
<p><strong>Unticketed PNRs</strong></p><br>

<p>Multi-GDS travel agents are encouraged to re-create PNR in other GDS -systems e.g. Amadeus, Travelport , Travelsky and issue ticket as per the fare rules. Original booking classes will be re-instated. Contact Finnair for re-instatement and cancellation of current PNR.</p><br>
<p><i>Alternatively</i></p><br>
<p>Ticket issuance is done via Finnair Contact Centers, acceptable form of payment is Credit Card only. Finnair will exempt first issue ticketing service fees.
Finnair will accept past date pricing for all fare types if original ticketing time limit is followed. Otherwise current fare pricing applies.</p>
<br>
<p><strong>Refunds</strong></p><br>
<p>Refunding tickets in Sabre and Abacus GDSs has been disabled.</p>
<p>BSP Travel Agents can send refund requests via BSPlink Refund Application (RA). When refund cannot be handled via Sabre/Abacus, the refund handling fee with BSPlink RA will be waived. The BSPlink RA should include the remark “Refund in Sabre/Abacus disabled”. The refund payment will be settled via BSP reporting. </p>
<p>US market ARC Travel Agents can submit the refund application by using the refund form on finnair.com. The WEB-form refund request should include additional information “Refund in Sabre/Abacus disabled”. The refund payment will be settled through ARC-IAR reporting (with agency credit memo).<br><br><br><br></p><p><strong>Cancelled ticketed PNRs</strong></p>

<p><br></p>

<p>There is an ongoing issue with
transferring the ticket numbers from Sabre/Abacus to Amadeus. Due to that
already ticketed PNRs may be cancelled by Finnair's ticketing control (this also affects European agencies). The
message "TKTL EXPIRED FOR AY - ITINERARY AUTOCANCELLED" is being
inserted into the PNR. Please contact Finnair for the reinstatement of the
flights.</p>

<b></b><i></i><u></u><sub></sub><sup></sup><strike></strike> </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_dist_sabre_abacus_stopped </guid> <pubDate> Tue, 26 Nov 2019 00:00:00 +0000 </pubDate> </item>   <item> <title>  25NOV instructions for reroutings due to IAU strike </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_25Nov_reroute_due_to_IAU_strike </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 25.11.2019 - 25NOV instructions for reroutings due to IAU strike </td> </tr> <tr> <td> <p>Due to IAU support strike Finnair allows rerouting on oneworld flights in case the original Finnair flight is cancelled.</p>

<p>Finnair is not a negotiating party on this labour dispute, but still Finnair and its customers are severely affected on this due to ground handling personnel going on strike at Helsinki airport.</p>

<p>Please follow our Info page at <a href="https://www.finnair.com/int/gb/flightinfo">finnair.com</a>.</p>

<table class="ay_table basic colored">
    <colgroup span="1"></colgroup>
    <thead>
        <tr>
            <th class="align-center" scope="colgroup" colspan="2">AY POLICY FOR VOLUNTARY REROUTINGS / REFUNDS / COMPENSATIONS FOR AY STOCK 105-TICKETED PAX</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>Cities affected</td>
            <td>All Finnair and Norra destinations</td>
        </tr>
        <tr>
            <td>Tickets issued by</td>
            <td>19.11.2019</td>
        </tr>
        <tr>
            <td>Ticket travel dates</td>
            <td>25.11.2019</td>
        </tr>
        <tr>
            <td>New travel dates</td>
            <td>21.11.2019 - 24.11.2019 or 26.11.2019 – 1.12.2019</td>
        </tr>
        <tr>
            <td>Inventory requirement, Booking class</td>
            <td>Same cabin class.</td>
        </tr>
        <tr>
            <td>Origin/Destination/Stopover changes</td>
            <td>No.</td>
        </tr>
        <tr>
            <td>Refund of tickets</td>
            <td>Only when flight is cancelled or if flight is delayed for 5 or more hours and customer wishes to cancel the flight</td>
        </tr>
        <tr>
            <td>Number of voluntary ticket changes</td>
            <td>1 free of charge, on second or more normal ticket rules apply</td>
        </tr>
        <tr>
            <td>Connections to other carriers</td>
            <td>Only AY or Norra operated flights can be rerouted, other carrier flights are not to be rebooked.</td>
        </tr>
        <tr>
            <td>Hotel accommodation</td>
            <td>No.</td>
        </tr>
        <tr>
            <td>SSR</td>
            <td>Rerouting due strike 25nov</td>
        </tr>
        <tr>
            <td>Rerouting</td>
            <td>AY, Norra and oneworld carriers are allowed</td>
        </tr>
    </tbody>
</table><p><br mce_bogus="1"></p>

<p><a href="https://www.finnair.com/int/gb/easy/reservation-and-ticketing/flight-irregularities/instructions-for-involuntary-reissue">Instructions for involuntary reissue are found here</a></p>
<p><a href="/go/2019.12-46/documents/PDFs/cancelled_flights_monday_25_11.pdf">List of cancelled flights 25Nov can be found here</a></p> </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_25Nov_reroute_due_to_IAU_strike </guid> <pubDate> Mon, 25 Nov 2019 00:00:00 +0000 </pubDate> </item>   <item> <title>  25NOV Guidelines for possible strike at HEL airport </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_25Nov Guidelines for possible strike at HEL airport </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 21.11.2019 - 25NOV Guidelines for possible strike at HEL airport </td> </tr> <tr> <td> <p>Due to the possibility of an upcoming strike Finnair allows VOLUNTARY rerouting on Finnair and Norra operated flights only. The Finnish Aviation Labour Union (IAU) has issued a support strike warning notice concerning the ground handling operations for the following time period: 25.11.2019.</p>
<br>
<p>Finnair is not a negotiating party on this labour dispute, but still Finnair and its customers could be severely affected on this threat due to ground handling personnel going on strike at Helsinki airport.</p>
<br>
<p>Please follow our Info page at <a href="https://www.finnair.com/int/gb/flightinfo">finnair.com</a>.</p>
<br>
<table class="ay_table basic colored">
    <colgroup span="1"></colgroup>
    <thead>
        <tr>
            <th class="align-center" scope="colgroup" colspan="2">AY POLICY FOR VOLUNTARY REROUTINGS / REFUNDS / COMPENSATIONS FOR AY STOCK 105-TICKETED PAX</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td>Cities affected</td>
            <td>All Finnair and Norra destinations</td>
        </tr>
        <tr>
            <td>Tickets issued by</td>
            <td>19.11.2019</td>
        </tr>
        <tr>
            <td>Ticket travel dates</td>
            <td>25.11.2019</td>
        </tr>
        <tr>
            <td>New travel dates</td>
            <td>21.11.2019 - 24.11.2019 or 26.11.2019 – 1.12.2019</td>
        </tr>
        <tr>
            <td>Inventory requirement, Booking class</td>
            <td>Same cabin class.</td>
        </tr>
        <tr>
            <td>Origin/Destination/Stopover changes</td>
            <td>No.</td>
        </tr>
        <tr>
            <td>Refund of tickets</td>
            <td>Only when flight is cancelled or if flight is delayed for 5 or more hours and customer wishes to cancel the flight</td>
        </tr>
        <tr>
            <td>Number of voluntary ticket changes</td>
            <td>1 free of charge, on second or more normal ticket rules apply</td>
        </tr>
        <tr>
            <td>Connections to other carriers</td>
            <td>Only AY or Norra operated flights can be rerouted, other carrier flights are not to be rebooked.</td>
        </tr>
        <tr>
            <td>Hotel accommodation</td>
            <td>No.</td>
        </tr>
        <tr>
            <td>SSR</td>
            <td>Rerouting due strike thread 25nov</td>
        </tr>
    </tbody>
</table><p><br mce_bogus="1"></p> </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_25Nov Guidelines for possible strike at HEL airport </guid> <pubDate> Thu, 21 Nov 2019 00:00:00 +0000 </pubDate> </item>   <item> <title>  Ticket Access enabled to Travel Agents who originally issued AY Tickets allowing them to further Display and perform Reissue/Exchange activities their end, even after Ticket reissue done by AY </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_Access enabled to Travel Agents who originally issued AY document allowing them to further process Refund or update Exchange activities their end </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 14.11.2019 - Ticket Access enabled to Travel Agents who originally issued AY Tickets allowing them to further Display and perform Reissue/Exchange activities their end, even after Ticket reissue done by AY </td> </tr> <tr> <td> <p>Amadeus Travel Agencies will now be able to access and take actions on AY Tickets issued by them even after there is Reissue performed by AY who then has control over it.&nbsp;<br><br>Earlier access was not allowed for further actions but with the activation of new Rule, Travel Agents will be able to display AY Tickets issued by them and further perform Reissue/Exchange actions their end when customer has still contacted them directly.&nbsp;<br>This function has been activated in Production dated 28th October 2019 and at the moment is available only for Amadeus Agencies but in future would be available for other GDS Agencies as well depending upon GDS readiness.&nbsp;<br><br>*For EMD in any situation only display access is allowed.<br></p> </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_Access enabled to Travel Agents who originally issued AY document allowing them to further process Refund or update Exchange activities their end </guid> <pubDate> Thu, 14 Nov 2019 00:00:00 +0000 </pubDate> </item>   <item> <title>  Changes to Tour Operator ticketing time limits and cancellation policy </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_ChangesToTourOperatorTicketingTimeLimitsAndCancellationPolicy </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 29.10.2019 - Changes to Tour Operator ticketing time limits and cancellation policy </td> </tr> <tr> <td> <p>Please be informed that the Ticketing Time Limit for AY TO-fares has been streamlined between markets. The new TTL’s and fare rules are in GDS now. The new TTL will be:<br><br></p>
<table class="ay_table basic colored">
    <colgroup span="3"></colgroup>
    <thead>
        <tr>
            <th class="align-center" scope="colgroup" colspan="3">Ticket Time Limit</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <th></th>
            <th id="Booking-days-to-departure" scope="col">Booking Days to departure</th>
            <th id="ticket-time-limit" scope="col">Ticket Time Limit</th>
        </tr>
        <tr>
            <th style="vertical-align: middle;" rowspan="6" scope="rowgroup">All Classes / Cabins</th>
            <td>60 days or more</td>
            <td>30 days after reservation</td>
        </tr>
        <tr>
            <td>31 - 59 days</td>
            <td>15 days after reservation</td>
        </tr>
        <tr>
            <td>21 - 30 days</td>
            <td>7 days after reservation</td>
        </tr>
        <tr>
            <td>06 - 20 days</td>
            <td>72 hrs after reservation</td>
        </tr>
        <tr>
            <td>02 - 05 days</td>
            <td>24 hrs after reservation</td>
        </tr>
        <tr>
            <td>00 - 01 days</td>
            <td>02 hrs after reservation</td>
        </tr>
    </tbody>
</table>
 </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_ChangesToTourOperatorTicketingTimeLimitsAndCancellationPolicy </guid> <pubDate> Tue, 29 Oct 2019 00:00:00 +0000 </pubDate> </item>   <item> <title>  Flights to Beijing’s new airport Daxing starting 03Nov </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_Flights to Beijing new airport Daxing starting 03Nov </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 04.10.2019 - Flights to Beijing’s new airport Daxing starting 03Nov </td> </tr> <tr> <td> <p>Finnair is
adding capacity to Beijing starting 03Nov 2019 with 3 operations to Beijing’s
new airport - Beijing Daxing airport in south Beijing. </p>

<p>As of 03Nov
2019 Finnair will operate to two airports in Beijing; Capital airport (PEK) 7
times per week and Daxing (PKX) 3 times per week.</p>

<p><br></p>

<p>The schedule
for Daxing in local times for winter 19:</p>

<p>AY81
HEL-PKX D137 17:10 - 07:10 on Monday, Wednesday and Sunday</p>

<p>AY82
PKX-HEL D124 11:10 - 14:05 on Monday, Tuesday and Thursday</p>

<p><br></p>

<p>Please pay
attention when booking flights to/from Beijing to avoid any mix up between the
two airports and advise passengers to go to the right airport.</p>

<p>Happy
sales!</p> </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_Flights to Beijing new airport Daxing starting 03Nov </guid> <pubDate> Fri, 4 Oct 2019 00:00:00 +0000 </pubDate> </item>   <item> <title>  Co-operation between AY/JP has ended </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_Co-operation between AY and JP has ended </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 02.10.2019 - Co-operation between AY/JP has ended </td> </tr> <tr> <td> <h1>Co-operation between AY/JP has ended</h1><p><span class="ms-rteThemeForeColor-2-5"><span><span>Please be advised that Finnair's&nbsp;partnership with JP/165/Adria Airways is<span>&nbsp;terminated&nbsp;</span><span>due to the their suspension of operations.<br></span></span><br>If passenger is holding an unused 105-ticket it can be refunded directly via GDS. In that case please remember to add OSI “FULL REFUND DUE TO JP INSOLVENCY” in the PNR. <br><br>Partial refunds will be handled via refund applications.<br><br></span></span></p><p><span class="ms-rteThemeForeColor-2-5"><span><br><span>Passengers with 165-ticket should contact JP for futher&nbsp;instruction.&nbsp;</span><br></span></span></p> </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_Co-operation between AY and JP has ended </guid> <pubDate> Wed, 2 Oct 2019 00:00:00 +0000 </pubDate> </item>   <item> <title>  CERTAIN APPLE MACBOOKPRO DEVICES ARE NOT ALLOWED ON FINNAIR FLIGHTS DUE TO BATTERY ISSUES </title> <link> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_CERTAIN APPLE MACBOOKPRO DEVICES ARE NOT ALLOWED ON FINNAIR FLIGHTS DUE TO BATTERY ISSUES </link> <description> <![CDATA[ <table cellspacing="0"> <tr> <td> 30.08.2019 - CERTAIN APPLE MACBOOKPRO DEVICES ARE NOT ALLOWED ON FINNAIR FLIGHTS DUE TO BATTERY ISSUES </td> </tr> <tr> <td> <span>The European Aviation Safety Agency EASA and the US Federal Aviation Administration have issued instructions regarding the 15-inch MacBook Pro units manufactured between Sept 2015 and Feb 2017 that are subject to the recall by Apple on June 20, 2019 due to battery issues.&nbsp;</span><span>Such devices are not allowed in checked-in baggage or onboard on Finnair flights before their batteries have been replaced. Customers are responsible for ensuring the status of their device before their flight via Apple webpages at https://support.apple.com/15-inch-macbook-pro-battery-recall</span> </td> </tr> </table> ]]> </description> <guid> https://www.finnair.com/int/gb/information-services/flights/news?ITEM_ID=508#NEWS_CERTAIN APPLE MACBOOKPRO DEVICES ARE NOT ALLOWED ON FINNAIR FLIGHTS DUE TO BATTERY ISSUES </guid> <pubDate> Fri, 30 Aug 2019 00:00:00 +0000 </pubDate> </item>  </channel> </rss>






