Georgealbert

Thanks, good information. Yes agree, we are never going to know, as this was not a reportable incident and there is no investigation. Only the airport management will now review their emergency response plan and the actions taken, then amend, update and train as required.

The RVP seemed was well organised, and announcements made over a speaker system to all emergency responders. This video is of the announcement that the aircraft and everyone on board had landed safely. RPReplay_Final1718513247.mov

Good points. i had a quick look through the basic A319 checklists, but I don’t have the technical knowledge, to know, if anything in the descend checks, may have alerted the pilots.

Saw the video of the rescue, (not going to post here) the van driver died instantly, the ambulance driver was in a very bad way, and took the longest to be released from the wreckage.

Link to the story, now in the media. https://workpointnews.com/around/news/NF9O9LN

These VIP companies keep their flight plans and manifest very secretive to protect the privacy of their customers. As there was no reportable incident, I doubt anything will become public. My own personal view is now leading me to believe this was a planned refuelling stop, hence the 68 minute turnaround time on the ground.The warning alert for the nose gear was detected on pre-landing checks on the approach to the airport, and the airport decided to put in a full emergency response plan as a precaution. Once on the ground the pilot received technical advice on solutions from home-base, and these were actioned, checked and okayed to proceed.. The aircraft only left Manila, today at approximately 09.00 this morning thai time and is heading north east currently. I can find no listed destination, but seems to be in the direction of Japan possibly.

Yes fully agree, but I am sure that is only in a standby mode, as the airport is not currently that busy. Normal day pictured below. It is how experienced the personal are that cover the hours out of normal operations.

Fully agree, I use flightradar app, and it is set up to receive 7700 alerts, but did not get one for this aircraft. The plane woke me up, as it made what sounded like a lower approach, and I was then informed of the details by someone at the RVP. The information briefings at the RVP, were not consistent, hence the reported changes in the numbers involved. It may had been this confusion on how many passengers, that led to the airport initiating a full emergency response. It is easier to send responders away if not needed, rather than be lacking in responders should it had been an accident. This occurred outside of normal operating hours, and I don’t know what the arrangements are at U-Tapeo, to maintain a standby ground team, to handle a declared emergency landing. There does seem to be a break down of communications somewhere in the chain from pilot, ATC, duty airport manager and emergency/crisis response, and it is not known how experienced some of these involved were.

Latest Thai media update. This accident happened on June 15, at 22:28 and involved a private van and an ambulance, and occurred, at the end of a four-lane road near Baan Hua Wua on the Buriram-Prakhonchai Road, Samed Subdistrict, Buriram. The accident claimed the life of one individual, a male who was driving the private van, and was traveling alone. The ambulance involved in the accident had four injured individuals: the driver, a nurse, an assistant, and a patient being transported to the provincial hospital.

Additional pictures from the scene, suggest the second van, was an ambulance.

Two vans collided in Ban Hua Wua, Samet Subdistrict, Mueang District, Buriram. The collision has resulted in multiple injuries, with some individuals trapped inside the vehicles and having to be cut from the wreckage by responders. There was 1 confirmed death at the scene. Preliminary reports indicate that the deceased was a music teacher from a high school in Prakhon Chai. Pictures by the Sawang Chanyatham Rescue Team from Prakhon Chai District.

Off topic, as this incident was a Airbus, but lets looks at the facts of your links, not just a couple of headlines on news sites. Southwest incident - most likely pilot error. “According to ADS-B Data the aircraft descended normally through about 950 feet MSL at 05:12:31 with a sink rate of about 800-1000 fpm, at 05:12:47 however the aircraft is seen climbing through 875 feet MSL at a high climbing rate. What happened in these 16 seconds is described in an internal memo circulating in Southwest Airlines stating, that during the go around due to weather conditions the first officer, pilot flying, inadvertently pushed the control column forward while monitoring the power settings causing the aircraft to descend to about 400 feet MSL before the aircraft started climbing again.” Tui incident - most likely pilot and maintenance issue. “The aircraft took off from Runway 09 with a thrust setting significantly below that required to achieve the correct takeoff performance. Rotation for the takeoff occurred only 260 m before the end of the runway and the aircraft passed over the end at a height of approximately 10 ft. The N1 required to achieve the required takeoff performance was 92.8% but, following an A/T disconnect when the crew selected TOGA, 84.5% was manually set instead. Despite an SOP requirement to check the thrust setting on takeoff, the crew did not realize that the thrust was not set correctly until after the takeoff although they had noted how close to the end of the runway they were.” The International Air Transport Association (IATA) 2023 Annual Safety Report for global aviation, states that aviation continues to make progress on safety with several 2023 parameters showing “best-ever” results. So the expert’s opinion is very different from your “The incidents getting worse every month”, but lets not let data and facts gets in the way.

Updated report says a female driving the pickup truck, experienced a tyre explosion, causing her to lose control and crash into the fuel dispenser. https://www.fm91bkk.com/newsarticle/31748

June 15, at approximately 18:00, volunteer rescue units from Surin, along with firefighting personnel, responded to an accident where a pickup truck crashed into fuel dispensers at an Esso gas station near the Do Home intersection in the Nok Mueang sub-district, Mueang district, Surin. Upon arrival, responders discovered a Mitsubishi Triton pickup truck had collided with the fuel pump, causing a fire. Firefighters from Nok Mueang Subdistrict Administrative Organisation, Surin City Municipality, and Salakdai Subdistrict Administrative Organisation successfully brought the blaze under control using water hose-lines. Fortunately, there were no injuries reported at the scene. However, the accident resulted in damage to two motorcycles, one car, and two fuel dispensers. Pictures from Surin rescue unit.

Fully agree. The flight distance between Dubai (Dubai International Airport) and Manila (Ninoy Aquino International Airport) is 4297 miles / 6915 kilometers / 3734 nautical miles. The company, Comlux Malta, in their literature says the aircraft has a range of 3900 nautical miles, so could have flown the route direct. (Airbus in their literature give a maximum range of 4600 nautical miles) https://comlux.com/aviation/fleet/airbus-acj-319-9h-liv https://www.acj.airbus.com/en/iflyacj/acj319-9h-liv

This is the 2 flight paths for the aircraft, leaving Dubai to U-Tapao, then onto Mailla.

Here is confirmation that this A319 aircraft, registration 9H -LIV, after taking off again from U-Tapao, did fly to the Philippines, landing at Manilla, at 05.49 PST.

Yes there may do, but the engineers would be from or retained by the airlines, and U-Tapao has 3 regular airlines using the airport; Bangkok Airways, which fly ATRs only there, FlyDubai, who's fleet are Boeing 737 Max 8, Thai Lion Air, which uses the Boeing 737 900. To get a suitable, qualified Airbus engineer there and do any repairs, I would expect to take longer that the 1 hour 8 minutes this Airbus319, operated by Comlux Malta, was on the ground.

Thanks, but I was lucky last night, as I knew a few people who were at the RVP. And this incident was more interesting than the Germany v Scotland game.

That would explain why ground services were available at that time of night, out of normal hours. I can find no evidence the pilot issued a swalk code or declared an emergency, but the airport did declare a full emergency when the aircraft was over the gulf of Thailand. All ambulances were in place at the RVP before the aircraft fly over them, and the Police had closed the main road under the flight path, before the plane landed. The initial emergency briefing, at the RVP, reported the plane had front landing gear problems, and this was when it was still on approach, but all emergency crews were only told to standby, with no-one proceeding airside.

Yes, the only reporters there were local news staff, and most of the story seems based on social media reports posted by responders, who were caught up in the chaos, excitement and rumours at the RVP. There have been zero official public statements from either the airport or airline involved.

Do you really think at 00.30, there was a suitable Airbus engineer available at the airport to manually fix a hydraulic leak, pass the aircraft fit for flight, all in the hour before it took off again. The only regular flights to the airport are by B737/Max, and ATR aircrafts. Only possible defect could have been a warning activation, which the pilots rectified by radio to an engineer at their base. Then running the check lists, so the plane could fly off.

I can’t see why it declared a full emergency, when it could of requested an emergency divert for one sick passenger, and hence just a small emergency response, if it wanted a ‘clandestine’ landing.

The airport will have a emergency response plan, which will detail what response and actions are needed for any incident type. Once the information from pilot is passed to ATC (Air traffic control), the airport duty manager, will put into action the suitable plan. Turn out of emergency response in the U-Tapeo area, would have been done by messages to radio control centres and then radio messages to all relevant agencies, required to respond. Ambulances from as far as Pattaya responded to this incident. The airport had also recently carried out an emergency response drill on May 30, 2024, when the Naval Aviation Division, Fleet Operations Command organised a emergency response, training exercise, to test the pre-determined plans for an aircraft accident at U-Tapao Airport. ICAO (International Civil Aviation Organisation), guidelines, require this type of exercise takes place twice a year. This incident involved a Thai Navy, Dornier Do-228-212, turboprop aircraft with multiple casualties, crashed on the airport apron. All airport and external agencies expected to respond in a real incident were involved, and there was pre exercise, refresher training, at the airport, between 24 - 30 May, to develop knowledge, cooperation, emergency planning/procedures, communications and incident command/management systems.

Most VIP companies block flight tracking in public apps. When the aircraft is in the air, its transporter is on and the flight path, airspeed, etc. can be seen. But you can not search the app. As the flights have no flight code. This was from last night.