Jalukbari · Maligaon · Paltan Bazaar · Pan Bazar
Closest city-side handovers after the airport release and a natural catchment for most Guwahati-city cases.
Plan roughly 25–60 minMove through each category. Hovering a parent opens the next level; moving back replaces the later columns.

For a Bangalore-to-Guwahati case, we arrange pickup, required preparation, BLR airport reporting, an accepted GAU movement and guidance for release at Guwahati Airport, followed by road transportation in Guwahati or onward movement to nearby Assam and Meghalaya destinations when required.
For most cases we check the nonstop BLR (Bangalore) → GAU (Guwahati) sector. GAU is Lokpriya Gopinath Bordoloi International Airport at Borjhar. After the required preparation in Bangalore and acceptance for the flight, the coffin is released on the cargo side and then moved by road to the final address in Guwahati or nearby destinations such as Shillong, Nongpoh, Nagaon or other planned locations.
Current nonstop passenger operators to GAU: Air India Express, Akasa Air and IndiGo. Passenger-seat availability does not confirm human-remains cargo acceptance.
Bangalore-side reporting follows the accepting airline's cargo instructions.
Also called Guwahati Airport or LGBI Airport in common use.
Approximate route distance between BLR and GAU.
Preparation, cargo reporting, release and road transfer are additional.


Keep the applicable death or medical document and identification ready. For the air cases we coordinate, embalming and coffin/packing certificates are required; MLC or postmortem cases also need the applicable police clearance/NOC and postmortem papers.
Full Bangalore document guideAt Guwahati, the passenger terminal and the cargo process are not the same collection point. The receiver should follow the exact airline or handler instruction shared for the accepted movement instead of assuming the normal arrival gate is the handover point.
Name, phone number and identification should be ready before the BLR movement is finalised.
The final Guwahati or Shillong road time is counted from the actual cargo release, not from the scheduled landing time.
Passenger flights operate daily, but human-remains movement still needs separate airline or handler acceptance before Bangalore airport reporting.
If the final destination is Shillong or Ri-Bhoi district, the airport release at GAU is followed by a longer hill-road transfer and should be planned with an additional time buffer.
Road transportation can be arranged after cargo release. These are practical planning buffers, not fixed driving promises; the final address, city traffic, highway conditions and hill-road travel all affect the last stretch.

Closest city-side handovers after the airport release and a natural catchment for most Guwahati-city cases.
Plan roughly 25–60 minCross-city movement toward the eastern side takes longer than the airport distance suggests, especially in peak traffic.
Plan roughly 45–90 minThe route can change according to bridge traffic and the exact receiving address on the north-bank side.
Plan roughly 45–95 minShillong is a common onward destination from GAU. The road climbs after Jorabat and needs a wider buffer than a flat-city transfer.
Plan roughly 2.5–4 hrsThese addresses are often covered by road from Guwahati when the accepted flight arrives at GAU and another airport does not offer a better overall route.
Plan roughly 2–4.5 hrsFor longer movements, we compare the final address, accepted flight and total road time before confirming whether GAU remains the best arrival gateway.
Plan case-by-caseIf the destination is Guwahati city or the Shillong side, changing the airport often adds more road complexity instead of solving it. We first check the next workable GAU movement. A different arrival airport is considered only when the final district truly supports it or another accepted route is clearly more practical.

For Guwahati, Dispur, Beltola, Nongpoh and Shillong-side handovers, GAU remains the natural gateway because it avoids an unnecessary extra airport transfer.
For Guwahati-city destinations, a later accepted GAU movement is often better than shifting the airport.The final destination may be in Meghalaya, but that does not automatically make Shillong Airport the better route. We compare the accepted flight options, total travel time and the real receiving address before suggesting any alternative.
For many Shillong-side cases, GAU plus road remains the more workable route.If the shipment is booked and accepted to GAU, the receiver follows the GAU release instruction. If another airport is separately accepted and genuinely shortens the overall movement, that route is considered case-by-case.
We compare the accepted flight, release process and final road distance before confirming the route.For Guwahati and Meghalaya-side destinations, GAU normally remains the first choice. We shift the airport plan only when the accepted routing and the real final destination clearly justify it.

The Bangalore air package is calculated within the included packed-cargo band up to 100 kg for eligible movements. The final quote is checked before work starts.
Final packed weight above the included band, airline cargo rate, case-specific requirements and any road transportation after GAU. The Guwahati, Shillong or outer-district road leg is quoted according to the final address and vehicle requirement.
The final address matters because Jalukbari, Dispur, Beltola, North Guwahati, Nongpoh and Shillong all require different road planning after the airport release.
Submitting opens WhatsApp with the route details ready to send.
The Bangalore guide carries the full document, preparation and cargo details. These answers stay with the BLR → GAU route and the Guwahati-side handover.