Complaint regarding baggage compensation from Malindo Air – India Consumer Forum

Complaint regarding baggage compensation from Malindo Air

I recently travelled through Malindo Air from Mumbai to Bali. My travel started on 07 Feb 2017 and I reached Bali on 08 Feb 2017. I went to baggage claim and I figured my baggage was not on board. I end up being in a foreign country with no personal belongings. Major emotional hit on my trip was that I travelled Bali for my honeymoon and the mishandling of luggage by airline spoiled my honeymoon trip.

I kept of following up with Malindo’s lost and found team in Bali as well as in Malaysia as Malaysia is the HQ for the airline company. My phone calls were not answered and emails were not responded. It used to take average turn around time of 2 days for them to reply on my emails. I was helpless and was forced to buy necessary belongings like clothes, cosmetics and was forced to have Mobile connection to have aggressive follow up as I lost hope to getting my luggage due you slow response.

On 13 Feb 2017 Malindo team was able to locate my luggage and they delivered it to me on 14 Feb 2017 when I was in Singapore. I had a trip to 2nd international destination and it costed me a lot for follow up phone calls and buying necessary items every day in a hope of getting my luggage tomorrow.

Passing through such a worse experience I have been offered a compensation of USD 60 one time for the total delay which is no where close to expenses made on phone calls for follow up, taxi charges to visit Bali airport to escalate the matter, to buy necessary clothes on daily basis and a cost of moral hit to my honeymoon trip

Kathan Bhatt
Nava Vadaj, Ahmedabad 380013, Gujarat
Email: kxxxxxxxxx0@gmail.com
120.60.6.149 / 16/02/2017 / 5:08 pm



Leave a Reply

Your email address will not be published.

Hello Consumers!

Do you have a consumer complaint? Why wait? Submit your complaint using our Post Complaints box. You will hear from us soon.
Note: Do not post complaints in the comment section

error: Content is protected !!