Indonesian ATR 42 Crashes Near Makassar, 11 Onboard Confirmed Dead

A government-contracted ATR 42-500 crashed near Makassar, Indonesia, during a surveillance mission on January 17, 2026. All 11 occupants died when the plane struck mountainous terrain on approach. While Sultan Hasanuddin International Airport remains open, flyers may face delays. Investigations by Basarnas and aviation authorities are focusing on wreckage recovery and ATC recordings from the incident's final moments.

Indonesian ATR 42 Crashes Near Makassar, 11 Onboard Confirmed Dead
Key Takeaways
  • An ATR 42-500 crashed near Makassar during a government maritime surveillance mission.
  • Authorities confirmed all 11 people onboard perished after the aircraft hit Mount Bulu Saraung.
  • Travelers should expect flight delays at Sultan Hasanuddin International Airport due to recovery operations.

(MAKASSAR, INDONESIA) — A fatal ATR 42-500 crash on approach to Makassar has triggered an official investigation and active search-and-recovery operations, which can ripple into flight schedules and information flow at Sultan Hasanuddin International Airport. If you’re flying through Makassar today or this weekend, expect tighter operational coordination, possible delays, and limited public detail because this was a non-passenger government mission.

Airport operations may continue but with added coordination for emergency response, and public updates will likely be limited while investigators and authorities process the scene and notifications. Travelers should plan for extra time and possible schedule impacts around UPG.

Indonesian ATR 42 Crashes Near Makassar, 11 Onboard Confirmed Dead
Indonesian ATR 42 Crashes Near Makassar, 11 Onboard Confirmed Dead
Before the crash After the crash (current situation)
Airport operations at UPG Routine arrivals and departures Operations continue, but with added coordination for helicopters, ATC workload, and response activity
Passenger rebooking waivers Normal fare rules No blanket passenger waiver applies, since this was not a commercial passenger flight
Public information Standard flight and passenger transparency Fewer immediate details, because it was a surveillance mission, not an airline service
What you may notice Normal connections and taxi times Extra buffers advised for check-in, connections, and reroutes if ATC flow slows

Key Date: The crash occurred on Saturday, January 17, 2026. If you’re traveling through Makassar this weekend, build in extra time.

1) Incident overview (confirmed facts vs early reports)

An Indonesia Air Transport ATR 42-500 went down in the Makassar area on the day of the incident while approaching Sultan Hasanuddin International Airport. Authorities have confirmed there were no survivors among the 11 people onboard.

Analyst Note
If you’re traveling through the same airports or carrier network, check both airport advisories and the airline’s disruption page before heading to the terminal. Keep your booking confirmation, and request rebooking/refund options in writing to document eligibility.

This was not a passenger flight. It was a marine surveillance mission linked to Indonesia’s Directorate General of Marine and Fisheries Resources Surveillance. That matters for travelers because mission flights often have different disclosure and reporting practices.

ATR 42-500 Makassar Incident: Confirmed Timeline (Initial Reports to Response)
  1. 1
    Completed
    Aircraft mission and pre-incident context (reconfigured as surveillance platform in April 2025)
  2. 2
    Completed
    Incident date: January 17, 2026
  3. 3
    Completed
    Departure: Yogyakarta (JOG) at 08:23 local (01:09 UTC)
  4. 4
    Completed
    Approach phase: Sultan Hasanuddin International (UPG) runway 21
  5. 5
    Urgent
    Loss of radar/radio contact: ~13:17 local
  6. 6
    Active
    SAR activation and multi-agency response (Basarnas, Indonesian Air Force, local authorities)
  7. 7
    Pending
    Operator/manufacturer support statement (ATR specialist support pledged)
→ Timeline status
Markers reflect sequence only; tags indicate semantic status (completed / urgent / active / pending) based strictly on provided items.

Passenger manifests, cabin counts, and publicly available details can take longer to settle. The investigation is now the central focus, and early reporting can shift as radar tracks, ATC logs, and on-scene findings are reviewed.

For broader context on how accident reporting develops over time, it’s worth comparing patterns seen in recent accident reports.

2) Flight details and route: what “approach corrections” can mean

The aircraft departed from Yogyakarta’s Adisutjipto Airport (JOG) and was inbound to Makassar (UPG). It was on approach to runway 21 at Sultan Hasanuddin International Airport when air traffic control attempted to correct the aircraft’s approach profile.

“Corrections” on approach can be routine. Controllers may issue headings, altitudes, or speed adjustments to re-sequence traffic, keep aircraft clear of terrain, or align them with the correct approach path.

Reports describe repeated attempts to correct the profile, followed by a loss of both radar and radio contact northeast of the runway. Investigators typically reconcile ATC recordings, radar data, and any onboard data to produce a single authoritative timeline.

Makassar ATR 42-500 Crash: Quick Reference (Confirmed/Early-Report Facts)
AircraftATR 42-512/500 (PK-THT), Serial 611
Role at time of flightNon-passenger marine surveillance mission
RouteYogyakarta (JOG) → Makassar (UPG)
Occupants11 onboard (early reports vary on breakdown)
OutcomeALL FATALITIES CONFIRMED
SiteMount Bulu Saraung area, ~5,100 ft elevation
Important Notice
After major accidents, misinformation and donation scams often spread quickly. Verify updates through Basarnas, the DGCA, the airport, or the airline’s official channels before sharing names, manifests, or fundraising links—especially posts that pressure for immediate payment.

For travelers, a major incident near a busy airport can increase controller workload and reduce arrival rates, meaning longer holds, longer vectors, and missed connections if you’re cutting it close.

3) Crash location and site: mountainous terrain raises the difficulty level

The aircraft impacted terrain on Mount Bulu Saraung in South Sulawesi, in a mountainous area outside Makassar. Initial public accounts included reports of an explosion and smoke, and climbers and local residents reported seeing debris.

Authorities later confirmed the outcome after locating the site. Mountain terrain changes everything: access is harder, weather shifts quickly, and rescue teams may face steep slopes and limited landing zones.

Even when airport weather looks manageable, the crash site can be very different only a short distance away. A second challenge is evidence preservation: debris can spread downslope and recovery teams must balance speed with careful documentation, because small details later matter in reconstruction.

4) Weather and terrain context: airport METARs don’t tell the whole story

Weather at Makassar’s airport around the period before the crash was reported as generally workable, including good visibility with showers in the area and convective clouds nearby. That kind of report can look “fine” to a casual reader.

The catch is that METARs describe conditions at the airport. They don’t fully capture en-route conditions or the localized effects that mountains can produce. Orographic lift can intensify clouds and precipitation on windward slopes, while valleys can trap haze and rain bands.

  • Weather radar and satellite imagery over the route
  • Pilot reports from other aircraft in the area
  • Terrain and obstacle data relevant to the approach
  • ATC instructions and altitude clearances

None of those items, on their own, proves a cause. They build a picture of the operating environment investigators will examine alongside other evidence.

5) Aircraft details and configuration: what a surveillance refit can involve

The aircraft was an ATR 42-500, also described as an ATR 42-512 variant. ATR 42s are common on short regional sectors across Asia because they handle thinner demand well and operate efficiently.

This particular aircraft had been reconfigured in 2025 as a surveillance platform. A refit like that can change the cabin layout and onboard equipment, introducing mission consoles, observation gear, extra comms equipment, or different seating arrangements.

That does not imply a mechanical issue by itself; it reflects the aircraft’s role. It was operated by Indonesia Air Transport under a maritime contract. The ATR 42 family typically uses Pratt & Whitney Canada turboprop engines in the PW120 series, paired with multi-blade propellers.

6) Occupants and casualties: why early counts can vary

Authorities have confirmed that all 11 onboard died. Early reporting sometimes varies on how many were “crew” versus “passengers” on a mission flight like this, and some occupants were reported to be linked to maritime or ministerial work.

That variability is common in the first news cycle, especially when a flight is not ticketed like a commercial service, multiple agencies are involved, and notifications to families are still underway.

The most respectful and accurate practice is to rely on confirmed totals and avoid overidentifying individuals until next-of-kin notification is complete.

7) Response and investigation: what happens next in Indonesia

Search and rescue operations involved Basarnas and other units, including air assets and ground teams. In mountainous terrain, weather and daylight can limit helicopter use, and ground teams often do the hardest work.

On the investigation side, Indonesia’s civil aviation authorities coordinate the formal process, consistent with international standards. The sequence usually includes securing the site, mapping the wreckage field, collecting ATC data, reviewing maintenance records, and interviewing relevant personnel.

Manufacturer support can be offered, but investigators retain control of findings. A key milestone is the handling of recorded data. If flight recorders or other onboard data sources are recovered, analysis can speed up clarity on the aircraft’s last minutes.

The role recorder work plays in moving from rumors to facts is illustrated by flight recorder analysis.

Warning

Expect early statements to focus on verified sequence and response actions. Causal language typically comes much later, if at all.

8) Operator context and governance: why info may come slower

Indonesia Air Transport operated the flight under a government-linked maritime surveillance mission. Government missions can change the tempo of public communication because multiple ministries and agencies may coordinate messaging and some operational details may be sensitive.

For travelers, that translates into two realities: you may not see the quick, familiar airline-style updates common after a passenger incident, and there may be fewer immediate “customer policy” moves like waivers, because the event did not involve commercial passengers.

What you should do if you’re flying through Makassar

If Makassar is on your itinerary today or tomorrow, pad your schedule. Arrive earlier than usual and protect tight connections. If you booked an award ticket, check your program’s same-day change or redeposit rules because a misconnect can cost miles and fees.

Keep screenshots of delay notices and communications, since some trip insurance claims require proof. If you’re on the fence about flying today, pick a routing with more buffer time through Sultan Hasanuddin International Airport, even if it costs a little more in cash or points.

What do you think? 90 reactions
Useful? 96%
Robert Pyne

Robert Pyne, a Professional Writer at VisaVerge.com, brings a wealth of knowledge and a unique storytelling ability to the team. Specializing in long-form articles and in-depth analyses, Robert's writing offers comprehensive insights into various aspects of immigration and global travel. His work not only informs but also engages readers, providing them with a deeper understanding of the topics that matter most in the world of travel and immigration.

Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments