Skip to content

Facebook Instagram Linkedin X-twitter Youtube

About Us
Contact Us
Advertisement

About Us
Contact Us
Advertisement

Aviation Newsletter

WhatsApp Channel

Search

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Search

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

Latest News
Aviation Today Perspectives
Aviation Jobs
About Us

News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Contact Us

Search

RejectedTakeoff

Miami, United States: An American Airlines flight bound for Bermuda aborted its takeoff at Miami International Airport after a business jet entered the active runway without authorization, prompting pilots to reject the departure and averting what could have become a serious runway collision. The incident occurred at approximately 6:00 p.m. local time on Friday, June 26, when American Airlines Flight 308, an Airbus A319 operating from Miami to Bermuda, had already been cleared for takeoff from Runway 8R. The aircraft was carrying 112 passengers and had accelerated to about 60 mph (approximately 52 knots) when the flight crew spotted another aircraft crossing the runway ahead. The crew immediately initiated a rejected takeoff, bringing the aircraft to a safe stop. According to the Federal Aviation Administration (FAA), the two aircraft came within approximately one-third of a mile (530 metres) of each other before the American Airlines pilots successfully avoided a potential collision. The second aircraft involved was NetJets Flight EJA434, a business jet that was being operated by a third-party maintenance vendor at the time of the incident. NetJets later clarified that the aircraft was not under the company's operational control during the runway incursion. Air traffic control (ATC) recordings revealed confusion over runway crossing instructions immediately after the incident. The controller told the business jet crew, "You just crossed an active runway." The pilot responded, "You just told me to cross the runway, sir." The controller replied, "No, we said Amerijet 461," indicating that the clearance had been issued to another aircraft rather than the NetJets-operated jet. The FAA confirmed that the business jet entered the runway without authorization and has launched an investigation into the runway incursion. American Airlines said in a statement that Flight 308 discontinued its takeoff after the crew observed another aircraft on the runway and thanked its pilots for their quick response. No injuries were reported among the 112 passengers or crew members aboard the American Airlines aircraft, and no injuries were reported to those aboard the business jet. The FAA has not publicly disclosed how many people were on board the business jet. Following the incident, Flight 308 remained on the ground while inspections were carried out before departing approximately two to two-and-a-half hours later. The aircraft subsequently arrived safely in Bermuda at about 11:40 p.m. local time. In a separate aviation safety incident the same day, a United Airlines Boeing 737 operating Flight 1513 from Key West, Florida, to Newark Liberty International Airport reported a near collision with a drone while descending toward Newark. The aircraft, carrying 106 passengers and five crew members, was at approximately 2,000 feet when the flight crew reported that they had "almost hit a drone," estimating it passed roughly 100 feet below the aircraft's flight path. Another pilot approaching Newark also reported seeing the drone. The flight landed safely, passengers deplaned normally, and no injuries were reported. The FAA has opened an investigation and reiterated that unauthorized drone operations near airports pose significant safety risks and may result in substantial fines or criminal penalties.

American Airlines Aborts Takeoff At Miami After Unauthorised Jet Crosses Active Runway

Aviation Today News Desk / June 30, 2026

Miami, United States: An American Airlines flight bound for Bermuda aborted its takeoff at Miami International Airport after a business […]

New Delhi, India: India's Aircraft Accident Investigation Bureau (AAIB) has released its preliminary findings into the serious incident involving a Swiss International Air Lines Airbus A330-343 that suffered a left-engine failure during takeoff at Delhi's Indira Gandhi International Airport, forcing the crew to reject takeoff and conduct an emergency evacuation. The incident occurred shortly after 1:27 a.m. local time on April 26, 2026, when Swiss flight LX147 was preparing to depart Delhi for Zurich with 245 people onboard, including 232 passengers and 13 crew members. According to the AAIB report, the aircraft involved was a 2012-built Airbus A330-343, registered HB-JHK, powered by Rolls-Royce Trent 772B-60 engines. The aircraft had arrived in Delhi earlier that day, operating flight LX146 from Zurich. Investigators noted that the inbound Zurich–Delhi flight was uneventful. While seven maintenance complaints were logged after arrival, all were described as routine and unrelated to the aircraft's engines, flight controls, serviceability, or controllability. The reported issues were addressed before the aircraft was cleared for the return flight to Switzerland. No abnormalities were detected during pre-flight inspections before LX147's departure from Delhi. The aircraft, parked at Stand A14, received pushback and startup clearance before taxiing to Runway 28 via taxiway J6. At 01:25:56 IST, air traffic control cleared the flight for takeoff with light winds reported from 210 degrees at one knot. Moments later, during the takeoff roll, the aircraft accelerated to approximately 106 knots. According to cockpit reports cited by investigators, the crew heard a loud bang as the No. 1 engine experienced a failure. Pilots reported seeing a large flame projecting forward from the left engine and observed the aircraft veering left. The crew immediately rejected the takeoff and brought the aircraft to a stop on Runway 28 between taxiways G1 and G2. After stopping, the flight crew informed air traffic controllers of the engine failure and requested emergency services. Communications recorded by investigators show that airport vehicles and crash fire tenders responded rapidly. Initially, responders observed smoke around the aircraft. As emergency personnel continued assessing the situation, reports indicated smoke near the left landing gear and subsequently fire near the right landing gear area. Fire crews began firefighting operations while coordinating with air traffic controllers and the flight crew. At approximately 01:35 IST, a full airport emergency was declared. Following confirmation of smoke and fire indications, both engines were shut down. Emergency evacuation procedures were initiated directly on the runway. Seven of the aircraft's eight evacuation slides were deployed and used to evacuate passengers and crew. All occupants successfully exited the aircraft. Four passengers sustained injuries during the evacuation and were transported for medical treatment. Airport responders reported that the fire had been completely extinguished by approximately 01:50 IST. The aircraft was later towed from the runway and parked at a remote stand. The airport terminated the full emergency status at 04:50 IST. Data obtained from the aircraft's post-flight report showed the first recorded warning was an "ENG 1 Stall" message at 01:27 IST during the takeoff roll. This was followed by multiple system messages including "ENG 1 FAIL," "AIR PACK 1+2 FAULT," "F/CTL RUD TRIM 1 FAULT," and "ENG 1 REV UNLOCKED." An "ENG 1 SHUTDOWN" message was subsequently recorded after the aircraft came to a stop. Investigators conducted an external inspection of the aircraft and found metallic debris near the exhaust section of the left engine along with soot and burn marks on the engine pylon behind the exhaust area. Notably, no damage was observed on the engine fan blades, and investigators reported no significant structural damage to the aircraft apart from minor dents likely caused during emergency slide deployment. A borescope inspection of the failed engine revealed extensive internal damage. Investigators discovered broken bolts and spacers from the high-pressure/intermediate-pressure bearing support assembly within the thrust reverser ducts. High-pressure bleed valves were also partially blocked by debris. Further examination identified significant damage to components within the engine core, including the High Pressure Turbine, Intermediate Pressure Turbine, Low Pressure Turbine, and High Pressure Compressor sections. Both the high-pressure and intermediate-pressure shafts were seized, preventing complete inspection. The AAIB stated that although severe internal engine damage was identified, investigators were unable to determine the precise cause of the engine failure during the initial borescope examination because the engine's rotating assemblies could not be fully inspected. Importantly, investigators found no evidence of an uncontained engine failure. The failed Rolls-Royce Trent 772B-60 engine was manufactured in 2009 and had accumulated more than 75,500 operating hours and 11,369 flight cycles. Records show the engine's last overhaul occurred in May 2016. Since that overhaul, it had accumulated nearly 40,000 additional flight hours before the incident. Both cockpit crew members were appropriately licensed and qualified on the Airbus A330. The captain had more than 18,600 total flight hours, while the first officer had accumulated more than 2,170 hours. AAIB investigators have removed and downloaded data from both the cockpit voice recorder and flight data recorder. Analysis of the recorded information is ongoing. The bureau said the damaged engine will be removed from the aircraft for a detailed examination aimed at identifying the root cause of the failure. Investigators are also reviewing maintenance records, operational documentation, air traffic control recordings, and witness statements. The investigation includes participation from international authorities and technical experts. France's Bureau d'Enquêtes et d'Analyses (BEA), Airbus, the European Union Aviation Safety Agency (EASA), Germany's BFU, the United Kingdom's AAIB, and Rolls-Royce representatives are assisting the Indian investigation under the provisions of ICAO Annex 13. The AAIB emphasized that the findings released so far are preliminary and subject to change as the investigation progresses. No interim safety recommendations have been issued at this stage.

AAIB Preliminary Report Finds No Evidence Of Uncontained Failure In Swiss A330 Engine Incident

Aviation Today News Desk / June 1, 2026

New Delhi, India: India’s Aircraft Accident Investigation Bureau (AAIB) has released its preliminary findings into the serious incident involving a

Muscat, Oman: An Air India Express Boeing 737-800 operating flight IX712 from Muscat to Kannur suffered significant damage during a nighttime takeoff attempt at Muscat International Airport on May 15 after the aircraft reportedly lined up with runway edge lights instead of the runway centreline, triggering a high-speed rejected takeoff and a formal accident investigation by Omani authorities. The incident came to public attention nearly nine days later, on May 24, after regulatory sources in Oman confirmed details of the occurrence. The 18-year-old Boeing 737-800 had been preparing to depart Muscat for the approximately three-hour service to Kannur on the night of May 15. During lineup for departure from Runway 26L, the aircraft allegedly tracked the right-hand runway edge lights rather than positioning itself on the runway centreline. As the aircraft accelerated for takeoff at approximately 9:10 pm local time after entering the runway via taxiway E7, the Boeing 737 struck multiple runway edge lights, destroying several of them during the takeoff roll. Flight crew reportedly aborted the takeoff after hearing a loud bang and receiving cockpit warnings. The aircraft sustained substantial damage during the incident. Reports stated that the nose landing gear was damaged, at least one tyre deflated, and hydraulic system leaks were observed after the rejected takeoff. Aviation sources also indicated that debris from shattered runway lights may have been ingested into the engines, potentially causing additional engine damage. The aircraft became disabled on the runway following the rejected takeoff, forcing passengers and crew to disembark directly onto the runway surface while emergency teams responded. However, authorities have not officially confirmed all operational details surrounding the evacuation sequence. The aircraft has reportedly remained grounded in Muscat since the incident while technical inspections and investigative work continue. Oman’s Air Accidents Investigation Sector (AAIS) has classified the occurrence as an “accident” rather than a minor incident, underlining the seriousness of the event. Investigators are now examining cockpit procedures, runway lighting conditions, pilot situational awareness, airport surface markings, and other operational factors that may have contributed to the alignment error during nighttime operations.

Air India Express Aircraft Damaged After Wrong Runway Alignment During Muscat Takeoff

Aviation Today News Desk / May 26, 2026

Muscat, Oman: An Air India Express Boeing 737-800 operating flight IX712 from Muscat to Kannur suffered significant damage during a

Hong Kong, China: A Malaysia Airlines passenger flight bound for Kuala Lumpur was forced to abort takeoff at Hong Kong International Airport on 11 May 2026 after the crew encountered a technical issue during the takeoff roll, which was later followed by a tyre burst. No injuries were reported among passengers or crew. The incident involved Malaysia Airlines Flight MH079, operated by a Boeing 737-800 aircraft. The aircraft had begun its scheduled departure from Hong Kong around 8:45 a.m. local time. According to airport and aviation reports, the takeoff appeared normal initially, but shortly after acceleration began, the flight crew detected an abnormal condition accompanied by a loud bang and strong vibration, prompting an immediate decision to reject the takeoff. The pilots executed a Rejected Takeoff (RTO) procedure and brought the aircraft to a controlled stop on the runway. During the deceleration phase, one of the main landing gear tyres reportedly burst. Early reports indicate that the tyre failure occurred after the takeoff was aborted rather than being the initial cause of the rejection. Emergency response teams were deployed immediately as the aircraft came to a stop. The aircraft was safely brought under control and later vacated the active runway with assistance. It was subsequently towed to a parking bay for inspection. All passengers and crew disembarked safely after the aircraft returned to the apron, and no injuries were reported. Following the incident, the south runway at Hong Kong International Airport was temporarily closed for inspection and safety checks. The closure resulted in minor operational disruptions, including short delays and adjustments to flight movements. Normal runway operations resumed shortly after clearance from airport authorities. The Airport Authority of Hong Kong confirmed that the incident involved a technical issue during the takeoff phase and that emergency services responded promptly. Authorities also confirmed that the tyre burst occurred during deceleration after the rejected takeoff, and not as a primary trigger before the decision to abort departure. The aircraft involved was identified as a Boeing 737-800 operating Malaysia Airlines Flight MH079 from Hong Kong to Kuala Lumpur International Airport. The flight was later cancelled, and the aircraft underwent initial engineering inspection to determine the cause of the malfunction. Preliminary aviation assessments suggest that investigations are focused on possible landing gear stress during the rejected takeoff sequence or a technical tyre failure. The aircraft’s braking and safety systems functioned as intended, preventing further escalation of the incident. Malaysia Airlines has stated that the aircraft has been withdrawn from service pending detailed inspection and engineering evaluation. Aviation authorities and technical teams are continuing to examine the incident as part of standard safety procedures following a rejected takeoff event.

Malaysia Airlines Flight Aborts Takeoff At Hong Kong After Technical Issue, Tyre Burst

Aviation Today News Desk / May 12, 2026

Hong Kong, China: A Malaysia Airlines passenger flight bound for Kuala Lumpur was forced to abort takeoff at Hong Kong

Engine Fire Forces High-Speed Abort Of SWISS Delhi–Zurich Flight; 5 Injuries Reported SEO DES: Around 245 people, including four infants were onboard. Four passengers and a crew member sustained minor injuries. Probe underway. SOCIAL: A Swiss International Air Lines Airbus A330 (LX147) aborted high-speed takeoff at Indira Gandhi International Airport after an engine fire. The aircraft stopped safely and evacuated passengers on the runway. Five people (4 passengers + 1 crew) sustained minor injuries, revised from an initial count of six; no fatalities were reported. A total of 228 passengers, 4 infants, and 13 crew were onboard. Some passengers reported evacuation delays and ground response issues. The airline has launched an investigation and is assisting affected passengers. New Delhi, India: A Swiss International Air Lines long-haul flight bound for Zurich was forced to abort takeoff at high speed at Indira Gandhi International Airport early Sunday after an engine caught fire, triggering an emergency evacuation on the runway that left several passengers injured. The aircraft, an operating flight LX147 from Delhi to Zurich, began its takeoff roll at approximately 1:08 AM when the crew detected a critical engine malfunction accompanied by flames. The aircraft had already accelerated to nearly 193 km/h when pilots initiated a rejected takeoff (RTO) , a high-risk, time-critical manoeuvre performed at high speed. The crew brought the aircraft to a controlled stop on the runway and immediately ordered an evacuation. Passengers and crew exited using emergency slides as airport fire and rescue services rushed to the scene. Authorities declared a full emergency, the highest level of airport alert, while firefighting teams quickly contained the blaze. Four passengers along with one crew member sustained injuries during the evacuation, largely attributed to slide descent and panic movement. Most injuries were reported as minor, including sprains and impact-related trauma. The injured were transported to medical facilities, including hospitals in Gurugram, for evaluation and treatment. The airline had earlier said that six passengers had been injured but revised the number. There were 228 passengers, four infants and 13 crew members on board the aircraft, which was an Airbus A330. Several passengers described a sudden and forceful braking event followed by confusion during evacuation. Some cited issues such as delays in opening certain exits and crowding near evacuation points. A few passengers also criticised the ground response, alleging inadequate coordination and delays in post-evacuation assistance, including transport and accommodation. “We are aware of an incident involving flight LX147 in Delhi. The crew aborted takeoff following an engine issue and initiated a precautionary evacuation. Passenger and crew safety is our top priority, and we are supporting those affected while working with authorities to investigate the matter”, SWISS said in a statement. Preliminary information indicates the incident originated from an engine failure leading to fire, though authorities have not yet confirmed the exact cause. Aviation and airline technical teams have begun a detailed investigation into the sequence of events, including engine performance, fire detection systems, and crew response. SWISS confirmed that the takeoff was aborted as a precaution following an engine issue and stated that passenger safety remained the priority. The airline has initiated standard safety and technical inspections and is assisting affected passengers with rebooking and accommodation.

Engine Fire Forces High-Speed Abort Of SWISS Delhi–Zurich Flight; 5 Injuries Reported

Aviation Today News Desk / April 27, 2026

New Delhi, India: A Swiss International Air Lines long-haul flight bound for Zurich was forced to abort takeoff at high

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

AVIATION TODAY brings the latest in aviation and aims to cater information to professionals and Aviation Enthusiasts about the Industry.

Quick Links

About Us
Contact Us
Services
Advertise
FAQ

Navigate

Latest News
Civil Aviation
Pilot Training
Flight School Analysis
Aviation Jobs
Training

General Support

info@aviationtoday.in

News Desk Support

news@aviationtoday.in

Follow Us

Facebook-f Instagram Linkedin-in X-twitter Youtube

© Copyright 2026 Aviation Today. All rights reserved.

Terms of Use
Privacy Policy
Disclaimer

Search

About Us
Latest News
Aviation Today Perspectives
Aviation Jobs
Contact Us
Advertisement

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube