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

Just In

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix
Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich
Two Dead After Light Aircraft Crashes In Remote Area Of North Wales, AAIB Investigates
India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru
SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash
Heart Aerospace X1 Completes First Flight As World’s Largest Battery-Electric Aircraft
South Korea’s Incheon Overtakes Dubai To Become World’s Busiest International Airport
FAA Orders 471 Boeing 737 MAX Jets To Undergo Crack Inspections Over Structural Risks
Air India Group Mandates Substance Screening For All Pilots Following A320neo Incident
China’s Homegrown C919 Makes International Debut With Air China Flight To Mongolia

SpiceJet to Expand Fleet, Invest in New Tech Amid ₹3,000 Crore Fundraising Success

Aviation Today News Desk

September 23, 2024

Add us on Google

Add us on Google

Just In

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix
Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich
Two Dead After Light Aircraft Crashes In Remote Area Of North Wales, AAIB Investigates
India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru
SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash
Heart Aerospace X1 Completes First Flight As World’s Largest Battery-Electric Aircraft
South Korea’s Incheon Overtakes Dubai To Become World’s Busiest International Airport
FAA Orders 471 Boeing 737 MAX Jets To Undergo Crack Inspections Over Structural Risks
Air India Group Mandates Substance Screening For All Pilots Following A320neo Incident
China’s Homegrown C919 Makes International Debut With Air China Flight To Mongolia

SpiceJet to Expand Fleet, Invest in New Tech Amid ₹3,000 Crore Fundraising Success

Aviation Today News Desk

September 23, 2024

Add us on Google

Add us on Google

Leave a Comment

You must be logged in to post a comment.

Follow on Google News

Join WhatsApp Channel

Subscribe to our Newsletter

Email

Recent News

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after two American Airlines Boeing 737-800s were simultaneously operating under the same “American 2482” callsign while flying in opposite directions between Phoenix and Chicago. One aircraft was arriving at Phoenix from Chicago O’Hare International Airport, while another had just departed Phoenix for Chicago. The unusual overlap occurred after the inbound Flight 2482 was delayed by weather, prompting American Airlines to use another aircraft already at Phoenix so passengers waiting for the outbound service could depart on schedule. Because Flight 2482 normally operates as a Chicago-Phoenix round trip using the same flight number, the replacement aircraft also operated under the 2482 identification. The resulting callsign duplication placed both aircraft in the same area of airspace while communicating on the same frequency. Flightradar24 reported that the arriving aircraft was descending through about 11,000 feet while the departing aircraft was climbing toward 9,000 feet when the duplication was recognized. The FAA said the aircraft maintained the required separation throughout the incident. The Phoenix air traffic controller quickly recognized the problem and began distinguishing the two aircraft as “American 2482 on the arrival” and “American 2482 on the departure.” The controller then kept the arriving aircraft above the departing aircraft and prevented the departure from climbing into the arrival’s altitude, maintaining vertical separation as their flight paths converged. The controller also alerted both crews to the other aircraft. Reports said the pilots were able to see each other while they were still miles apart, providing an additional layer of awareness as the two aircraft crossed paths. No source has publicly released an exact minimum horizontal distance between the aircraft, and the FAA has confirmed only that required separation was maintained. The incident was captured in air traffic control audio published by ATC.com and subsequently highlighted by media outlets. After the departing aircraft had cleared the area, the controller said, “I’ve been working air traffic for 25 years. I’ve never seen two aircraft pretty much merge with the same call sign. That’s pretty incredible.” The arriving pilot later complimented the controller, saying “nice work.” The controller responded, “It could have been disastrous, but I’m glad it worked out.” The precise passenger and crew numbers aboard the two Boeing 737-800s have not been publicly disclosed by the FAA or American Airlines. Both aircraft completed their flights safely, with no injuries or collision reported. American Airlines said, “The diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed. Both flights continued safely and without incident.” Aviation safety expert Steve Arroyo, a former airline dispatcher and pilot, said the incident likely resulted from an oversight within the airline’s dispatch operation. He told Associated Press that someone should have identified that the two aircraft would be airborne at the same time under identical flight numbers. Arroyo described the event as an example of the aviation system’s ability to recover from an error once it reaches another safety layer. The FAA and American Airlines are investigating how the duplicate callsign was allowed to occur. The investigation will determine how the delayed inbound flight and the replacement outbound aircraft were planned and identified, and why the normal safeguards for avoiding simultaneous use of the same callsign did not prevent the situation.

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

August 17, 2026

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich SEO DES: The crew climbed to 9,000 feet and remained near Munich for two hours; Returned after tail-contact and low-tyre-pressure warnings, with damage SOCIAL: A Vietnam Airlines Boeing 787-9 flying from Munich to Hanoi took an unusually long takeoff roll on Runway 26L on August 15, 2026, before becoming airborne near the runway end. The aircraft reportedly travelled about 120 metres beyond the paved surface, with a tailstrike occurring during the late rotation. After takeoff, the crew climbed to around 9,000 feet and remained near Munich for about two hours before returning to the airport after warnings for tail contact and low tyre pressure. The aircraft sustained tail, landing-gear and tyre damage and could not taxi away after landing. The aircraft carried 271 passengers and 16 crew, all of whom were reported safe with no injuries. German authorities are leading the investigation, with Vietnamese investigators assisting, while the exact cause of the prolonged takeoff remains under investigation. Munich, Germany: A Vietnam Airlines Boeing 787-9 bound for Hanoi took an unusually long takeoff run from Munich Airport on August 15 before finally becoming airborne beyond the normal paved runway area, in an incident that resulted in runway damage, a tail strike and subsequent damage to the aircraft's landing gear. The aircraft later returned to Munich after remaining airborne for about two hours, with no injuries reported among the passengers or crew. The exact reason for the aircraft's prolonged acceleration and extremely late liftoff remains under investigation. The most significant part of the incident occurred during the takeoff roll. Video footage recorded from inside the cabin and from outside the airport shows the 787 accelerating along Runway 26L for an unusually long distance before rotation. Instead of lifting off with substantial runway remaining, the aircraft continued almost to the end of the approximately 4,000-metre runway. Reports based on flight-tracking data indicate that the aircraft reached the runway end area before becoming airborne, with reports putting the excursion beyond the paved surface at roughly 120 metres. The available video is particularly significant because it shows that the issue was not simply a conventional tailstrike during an otherwise normal rotation. The aircraft appears to remain on the ground for an unusually long period, with the runway threshold passing while the aircraft was still accelerating. It eventually rotated at the very end of the runway area, after which a large cloud of dust was visible beneath the rear of the aircraft. The reason for the unusually slow or prolonged takeoff has not been established. Online speculation has included possibilities such as an incorrect takeoff configuration, incorrect thrust or a problem affecting the aircraft's acceleration. However, none of those explanations has been confirmed by Vietnam Airlines or investigators and should not be presented as the cause. Vietnam Airlines has described the event as resulting from a technical issue and said the crew followed safety procedures. The airline has not publicly identified a specific technical failure responsible for the aircraft's unusually long takeoff roll. That distinction is important because the aircraft's subsequent warnings and damage do not, by themselves, establish what caused the initial lack of acceleration. Vietnam's aviation authorities have provided additional information on what happened after the aircraft became airborne. According to the latest reporting on the Civil Aviation Authority of Vietnam's information, warnings indicating tail contact and low tyre pressure were triggered shortly after takeoff. The authorities said the aircraft subsequently returned to Munich, while German authorities led the investigation with Vietnamese investigators assisting. After the aircraft finally lifted off, the crew did not immediately attempt to land. The Boeing 787 climbed to around 9,000 feet and remained in the Munich area for approximately two hours. During that period, the crew assessed the situation and reduced the aircraft's weight before returning to the airport. The tailstrike occurred as the aircraft became airborne after the exceptionally long takeoff run. The rear underside of the aircraft contacted the ground, producing the visible dust plume captured on video. A tailstrike can damage the aircraft's lower aft fuselage, pressure vessel, structural frames, systems, wiring and other components around the tail area. In this case, photographs and video circulating after the incident showed damage around the rear fuselage and the loss or damage of the Boeing 787's tailstrike protection component. The full extent of the structural damage, however, remains subject to technical inspection. The aircraft also sustained landing-gear and tyre damage. Reports indicate that several tyres were damaged or deflated, and footage following the return showed the aircraft unable to taxi away from the runway under its own power. The landing-gear damage also resulted in debris being left on the runway. The aircraft eventually landed back at Munich Airport, using the airport's other runway. Following the landing, the affected aircraft remained on the runway, forcing the closure of the runway and requiring airport authorities to clear debris and deal with the disabled aircraft. Traffic was subsequently handled through the other available runway, causing disruption at the German hub. There were no reported injuries among the passengers or crew. The aircraft was carrying passengers and crew on the Munich-Hanoi service; Vietnam Airlines has reported the total as 271 passengers and 16 crew members. All occupants were reported safe after the aircraft returned to Munich. The incident is now being examined by the relevant German authorities, with Vietnamese aviation investigators assisting. Investigators will need to establish why the Boeing 787 did not achieve the expected acceleration during the takeoff roll, why the aircraft reached the end of the runway area before becoming airborne and whether any technical, operational or performance-related factor contributed to the event.

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich

August 17, 2026

Trawsfynydd, United Kingdom: Two people have died after a light aircraft crashed in a remote area near Trawsfynydd, Gwynedd, North Wales, on August 14, after failing to arrive at Caernarfon Airport as scheduled. North Wales Police said it received reports shortly after midday that the aircraft, which had been travelling from an airfield in England, had not reached its destination. A multi-agency air and ground search was launched, with the aircraft eventually located in a remote area near Trawsfynydd. Both people on board were pronounced dead at the scene. The Air Accidents Investigation Branch (AAIB) has been notified and deployed a team of investigators to the site. The incident came to light shortly after noon when the aircraft failed to arrive at Caernarfon Airport, its scheduled destination. Police and partner agencies then began searching for the missing aircraft from the air and ground. The remote location of the wreckage near Trawsfynydd made the operation challenging, although police have not publicly disclosed the exact crash site. North Wales Police Chief Superintendent Owain Llewellyn said: “This has been a challenging search operation,” while thanking the agencies involved for their professionalism and dedication. Police have not released details of what caused the aircraft to crash, and there is currently no official indication that a mechanical failure, weather conditions, pilot action or any other factor was responsible. The AAIB is now leading the technical investigation, meaning any explanation of the circumstances remains premature. The police said they would support the AAIB investigation “to ensure the circumstances leading to this incident are fully understood.” The two occupants were the only people confirmed to have been on board, and both died at the crash site. Their identities have not yet been released publicly by North Wales Police. No official information has also been released on their ages, nationalities, whether one was the pilot and the other a passenger, or their relationship to each other. Police said specialist officers would support the families and friends of those involved. Chief Superintendent Llewellyn said: “Our thoughts are with the families and friends of those involved in this tragic incident.” The aircraft was travelling from an airfield in England towards Caernarfon Airport in Gwynedd. However, neither North Wales Police nor the media reports available so far have identified the departure airfield. The exact route, flight purpose and planned arrival time have also not been disclosed. Details about the aircraft itself also remain limited. Authorities have described it only as a “light aircraft”. Its manufacturer, model, registration, operator and owner have not been publicly confirmed in the official police statement or the initial media reports reviewed for this report. Until those details are confirmed by the AAIB, police, the aircraft registry or another authoritative source, they should not be attributed to the aircraft involved. The search involved multiple agencies using both air and ground resources before the aircraft was located. The police have praised the emergency agencies involved, but the initial statement does not provide a full list of participating organisations, the number of rescuers deployed, the aircraft or helicopters used in the search, or how long it took to locate the wreckage. Those details may emerge as the investigation and recovery operation progresses. The AAIB has now sent investigators to the scene. Its role is to establish the circumstances and probable cause of the accident and, where appropriate, make safety recommendations. No preliminary findings from the investigation have been publicly released.

Two Dead After Light Aircraft Crashes In Remote Area Of North Wales, AAIB Investigates

August 17, 2026

Bengaluru, India: India is targeting the introduction of electric air taxis by 2028, with Union Civil Aviation Minister Ram Mohan Naidu saying testing of electric vertical take-off and landing (eVTOL) aircraft is expected to accelerate from 2027. The latest development comes as Bengaluru-based Sarla Aviation has secured Design Organisation Approval (DOA) from the Directorate General of Civil Aviation (DGCA), a key regulatory step toward type certification of its indigenous eVTOL aircraft. The approval was handed over to Sarla Aviation at the inauguration of its new Bengaluru headquarters on August 8, 2026. Naidu said India wants to see the aircraft operating by 2028. “By 2028, we want to see these machines fly in India. There is a huge requirement, not only in Bangalore, but Mumbai and Delhi,” he said. He added, “I expect that next year we'll be completely in the testing phase,” while reiterating, “By 2028, we plan to make this happen.” Sarla Aviation has also moved beyond the early prototype stage. On July 1, 2026, the company announced that its half-scale Sylla 1.0 eVTOL technology demonstrator had completed more than 500 tests and over 18 hours of flight testing during a six-month campaign. The 700-kg-class aircraft has a 7.5-metre wingspan and, according to Sarla, became the heaviest electric aircraft to take off in India. The programme tested the aircraft's electric propulsion, battery architecture, distributed propulsion, flight controls, airframe and landing gear as an integrated system. Sarla Aviation CTO and co-founder Rakesh Gaonkar said the Sylla programme had produced the data needed to guide the next stage of development. “Sylla has given us the data we set out to capture, and those learnings are already shaping our next-gen aircraft as we move towards transition and sustained wing-borne flight on our journey to our 6+1 air taxi Shunya,” he said. The next step is Sylla 2.0, which is intended to demonstrate controlled transition from hover to sustained wing-borne flight. That is an important stage before the company moves toward a certifiable passenger-carrying eVTOL. Sarla's planned production aircraft is the six-passenger-plus-pilot Shunya. The developments provide an important update to the electric-air-taxi plan outlined by ET Now. The publication reported that India had set a 2028 target for eVTOL aircraft, with Naidu saying testing would gather pace the following year. The report highlighted Bengaluru, Mumbai and Delhi as cities where demand for such aircraft could be particularly significant because of severe road congestion and lengthy airport-city journeys. An eVTOL is an electrically powered aircraft capable of vertical take-off and landing. Unlike conventional fixed-wing aircraft, it does not require a conventional runway and can potentially operate from smaller facilities closer to urban centres. The technology combines characteristics associated with helicopters, drones and conventional aircraft and is being developed under the broader advanced-air-mobility sector. Sarla Aviation's Shunya is designed around seven electric motors. Six motors provide vertical lift, while a seventh motor mounted at the rear provides forward propulsion. Sarla Aviation co-founder and CEO Adrian Schmidt explained the configuration to ANI: “It's powered by six electric motors that lift it up and one in the rear that pushes it forward. So we have a total of seven electric motors that we're using and it's piloted as of now with six passengers.” The company has said the aircraft's propulsion remains electrically driven. However, Schmidt explained that the design leaves room for a turbo-generator that could potentially recharge the batteries during flight. “We have enough space allocation so that we can consider putting in a turbo generator to charge our batteries mid-flight. But the energy transition from the battery to the motors is always going to be purely electric,” he said. Sarla first unveiled the Shunya prototype at the Bharat Mobility Global Expo in New Delhi in January 2025. The aircraft was presented as a six-passenger eVTOL with a maximum payload of about 680 kg and a targeted top speed of up to 250 km/h. The company said it was designed primarily for short urban journeys of roughly 20–30 km, while reported specifications indicated a potential range of up to 160 km with available battery technology. Sarla's roadmap has also included infrastructure and manufacturing. In November 2025, the company signed an MoU with the Andhra Pradesh government for a 500-acre aerospace campus in Anantapur, with an initial investment of ₹1,300 crore. Sarla described the project as an integrated Urban Air Mobility facility for eVTOL manufacturing and related activities. The company has said the facility is intended to support future aircraft production and air-taxi operations. The company's airport strategy also began taking shape earlier. Sarla Aviation and Bengaluru International Airport Limited signed a partnership agreement in January 2024 to explore an eVTOL ecosystem at Bengaluru airport, including connectivity between the airport and urban areas, vertiport infrastructure and an advanced traffic-management system for future eVTOL operations. Healthcare is another potential application. Bengaluru airport had an agreement with Sarla Aviation for last-mile connectivity and that Manipal Hospitals had also entered an agreement with the company for potential air-ambulance operations. More recent industry reporting indicates that hospitals and air-ambulance operators are increasingly exploring eVTOL partnerships as India develops its advanced-air-mobility ecosystem. The possible uses therefore extend beyond passenger air taxis. The technology could support airport-to-city transfers, last-mile connectivity, air ambulance operations, medical evacuation and cargo transportation. For India, airport connectivity is expected to be one of the earliest practical applications because road journeys between major airports and city centres can take considerable time. Naidu has said an airport-to-city journey that currently takes as long as two hours could potentially be reduced to around 20–30 minutes using eVTOL aircraft. The initial model is therefore expected to focus on short-distance and airport-linked journeys rather than replacing conventional public transportation. The Indian eVTOL market is not limited to Sarla Aviation. Chennai-based The ePlane Company is developing its e200X electric aircraft, while Hyderabad-based BluJ Aerospace is working on eVTOL technology for cargo and other applications. India is therefore developing multiple domestic approaches to advanced air mobility rather than relying solely on one manufacturer. There is also an international dimension to India's air-taxi plans. In 2023, InterGlobe Enterprises, the parent company of IndiGo, announced a partnership with US-based Archer Aviation to explore an all-electric air-taxi service in India, with an original 2026 target. However, that timeline has not materialised as initially envisaged. In 2026, IndiGo Ventures separately invested about ₹10 crore in Sarla Aviation, giving the Indian startup additional strategic backing. Importantly, the IndiGo investment should not be presented as confirmation that IndiGo itself will operate Sarla's eVTOL air-taxi service. Recent reporting said Sarla Aviation clarified that IndiGo's investment did not mean the airline was directly involved in its eVTOL operating plans. The regulatory process remains one of the biggest hurdles. Before commercial passenger operations can begin, eVTOL aircraft must demonstrate compliance with safety and airworthiness requirements and obtain the necessary certification. The DGCA will have to address aircraft design, flight operations, pilot qualifications, infrastructure, vertiports and integration with existing air-traffic systems. Infrastructure is another challenge. Commercial operations will require suitable landing and take-off locations, charging or energy infrastructure, maintenance facilities and systems for managing eVTOL traffic around densely populated areas. Battery performance, aircraft range, weather, operating economics and air-traffic management will also influence whether the 2028 target can be achieved at scale. Sarla's progress in 2026 nevertheless represents a significant shift from the concept and prototype phase. With the Sylla demonstrator having completed an extensive flight-test campaign and the company now holding DGCA Design Organisation Approval, its Shunya programme has entered a more advanced development and certification phase. The government's 2028 target will now depend on the pace of testing, transition-flight development, type certification, infrastructure creation and operational approvals over the next two years.

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

August 16, 2026

Fochville, South Africa: The preliminary accident report, released on 28 July 2026 by the Accident and Incident Investigations Division (AIID) of the South African Civil Aviation Authority (SACAA), found that the engine of a Bird Aviation Piper PA-28-180 registered ZS-ESZ was not producing power when the aircraft struck the ground near Fochville, Gauteng, on 27 June 2026. The report remains preliminary, with the investigation still ongoing and the AIID cautioning that its findings do not apportion blame or liability. According to the report, the operator was Bird Aviation, while the aircraft was being used under a hire-and-fly arrangement for hour-building. The operation was classified as Training under Part 91, and the aircraft belonged to the approved training organisation (ATO) from which it was hired. The accident involved two people, a 21-year-old Indian pilot and one passenger. Both were fatally injured and the aircraft was destroyed. The pilot held a valid Private Pilot Licence (PPL) and was building flight hours toward a Commercial Pilot Licence (CPL) through the ATO. The flight took place on the afternoon of 27 June 2026, when the pilot and passenger departed Lanseria International Airport (FALA) in Gauteng on an hour-building flight, intending to return to the same airport. The flight was conducted under visual meteorological conditions (VMC) and in accordance with Part 91 of the Civil Aviation Regulations. The flight had initially been planned for 0900Z, but departure was delayed because of persistent haze and low visibility. After conditions improved, the aircraft departed Runway 07 at 1325Z, as confirmed by an air traffic control officer at Lanseria. It then flew toward the Johannesburg General Flying Area (GFA), Flight Area Dangerous 182 (FAD 182). Multiple eyewitnesses later reported seeing the aircraft flying unusually low and performing unfamiliar manoeuvres. The aircraft subsequently flipped and began spinning to the left before impacting the ground. The crash occurred on a farm at Elandsfontein, south-east of Fochville, Gauteng, at coordinates 26° 35' 27.30" South, 27° 33' 41.24" East, with a field elevation of 5,124 feet. The accident was recorded at 1415Z. The pilot was a 21-year-old Indian national with a valid PPL. His licence was initially issued by the regulator on 25 May 2026 and was valid until 30 April 2027. His Class 2 aviation medical certificate was issued on 26 March 2025 and was valid until 31 March 2030. The report states that the aircraft type was endorsed on his licence and that he had no previous accidents recorded in relation to the investigation. The pilot had accumulated 132.2 total flight hours, including 19.4 hours in the previous seven days and 55.1 hours in the previous 90 days. He had flown 43.8 hours on the aircraft during the previous 90 days and had accumulated 122.7 hours on the Piper PA-28-180. The aircraft was a 1977-built Piper PA-28-180, a four-seat, single-engine, all-metal, low-wing aircraft with fixed tricycle landing gear. It was powered by a four-cylinder, naturally aspirated 180-horsepower Lycoming O-360-series engine. Its serial number was 28-3303, and it had accumulated 3,242.6 airframe hours by the time of the accident. The AIID found that the aircraft had valid registration and airworthiness documentation. Its current Certificate of Registration had been issued on 19 September 2025, while its latest Certificate of Airworthiness was valid until 31 October 2026. The aircraft underwent its mandatory periodic inspection on 13 March 2026 at 3,218.4 airframe hours, after which a Certificate of Release to Service was issued, valid until 12 March 2027 or 3,318.4 total airframe hours, whichever came first. The aircraft was maintained by an approved aircraft maintenance organisation whose certificate was valid until 30 June 2026. The organisation held Category A and Category C ratings for the aircraft's airframe and engine. The ATO's certificate had been renewed on 17 November 2025 and was valid until 28 February 2029. Fuel records showed that 111 litres of Avgas 100LL had been uplifted after the aircraft's flight on 26 June 2026, with the pilot refuelling the tanks before parking the aircraft. The Piper PA-28-180 has a fuel capacity of 189 litres, providing approximately six hours of endurance. The preliminary findings state that the aircraft departed Lanseria with full fuel tanks and no technical issues. However, fuel was found leaking from the aircraft after the accident. The report does not currently identify the fuel leak as the cause of the engine power loss. Weather conditions were favourable and were not considered a contributing factor. The 1400Z METAR from Lanseria recorded winds from 300° at 7 knots, CAVOK visibility, a temperature of 16°C, scattered clouds at 4,500 feet, a dew point of 5°C and QNH of 1026 hPa. The aircraft's navigation and communication equipment had no recorded defects before the flight. It was not equipped with a flight data recorder (FDR) or cockpit voice recorder (CVR), and the report states that neither was required for this aircraft type. The wreckage examination showed that the aircraft hit the ground in a steep nose-down attitude at high speed with little forward momentum. The debris was concentrated around the impact point, with a crater being the only ground scar identified. The aircraft came to rest facing south-east. Investigators found that the ailerons could not be moved and were both in the down position, while the elevator and rudder moved freely. The landing gear had broken and collapsed rearwards. Both wings suffered severe leading-edge damage and accordion-like deformation that ruptured the fuel tanks. The damage was consistent with heavy compressive loading during the steep, rapid-impact sequence. The top engine cowling had separated from the aircraft and was found approximately 10 metres ahead of the main wreckage. The engine cradle was deformed and the engine was facing slightly to the right. The propeller showed asymmetric damage, with one blade bent rearwards and the other showing little or no deformation. Neither blade displayed S-curve bending. The AIID said the damage pattern was consistent with the propeller being non-rotating at impact. This evidence, together with eyewitness accounts of the pilot apparently attempting to restart the engine, led investigators to conclude that the engine was not producing power at the time of impact. However, the preliminary report does not yet establish the underlying reason for the loss of engine power. The instrument panel was broken into multiple pieces, with several indicators dislodged from their original positions. The report does not provide a final interpretation of the instrument evidence at this stage. There was no evidence of a pre- or post-impact fire. Investigators considered the accident not survivable because of the extent of cockpit damage. Emergency responders reported that the pilot-in-command was not wearing his seat belt and was consequently thrown from the aircraft. Medical and pathological information is reserved for the final report. The aircraft was operating in the Johannesburg GFA within FAD 182, outside the Terminal Control Area. FAD 182 extends from the ground to Flight Level 100, or 10,000 feet, except where it intersects the TMA. Bird Aviation also used the Safely Track Me application to monitor flights. The system relied on the pilot's mobile-phone GPS signal. Tracking was active when ZS-ESZ departed Lanseria, but shortly after the aircraft exited the Johannesburg Special Rules Area West TMA, the phone stopped transmitting its GPS position and the aircraft could no longer be tracked through the application. The AIID's preliminary findings confirm that the pilot was qualified and medically fit for the flight, the aircraft was being used under a valid hire-and-fly arrangement for hour-building, the operator/ATO held a valid certificate, the aircraft had valid registration and airworthiness documentation, and its maintenance records were up to date. The investigation therefore establishes several key facts but has not yet determined the precise cause of the accident. The aircraft left Lanseria with full fuel and no known technical issues; the engine was not producing power at impact; weather was not a factor; and the aircraft entered a steep, high-speed descent before striking the ground. The AIID is continuing to examine other aspects of the accident that could have safety implications. No safety recommendations have been issued at this stage. The AIID said these will be addressed in the final report. The investigation was classified as a Category 1 accident. The AIID appointed an investigator-in-charge and a co-investigator, dispatched investigators to the site and notified the relevant states and organisations under South African regulations and ICAO Annex 13. The AIID will lead the investigation and issue the final report. The AIID has warned that the preliminary report is based on evidence gathered during an ongoing investigation and that information may change if additional evidence emerges. Accordingly, the current finding should be described as the engine not producing power at impact, rather than stating that investigators have already determined the cause of the engine power loss.

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

August 15, 2026

Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 6

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 6

July 25, 2026

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 5

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 5

July 23, 2026

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - PART 4

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 4

July 21, 2026

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Citywide Networks Must Be Designed Around Real Travel Patterns

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 3

July 19, 2026

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Part 2- Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 2

July 17, 2026

Follow on Google News

Join WhatsApp Channel

Subscribe to our Newsletter

Email

Recent News

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after two American Airlines Boeing 737-800s were simultaneously operating under the same “American 2482” callsign while flying in opposite directions between Phoenix and Chicago. One aircraft was arriving at Phoenix from Chicago O’Hare International Airport, while another had just departed Phoenix for Chicago. The unusual overlap occurred after the inbound Flight 2482 was delayed by weather, prompting American Airlines to use another aircraft already at Phoenix so passengers waiting for the outbound service could depart on schedule. Because Flight 2482 normally operates as a Chicago-Phoenix round trip using the same flight number, the replacement aircraft also operated under the 2482 identification. The resulting callsign duplication placed both aircraft in the same area of airspace while communicating on the same frequency. Flightradar24 reported that the arriving aircraft was descending through about 11,000 feet while the departing aircraft was climbing toward 9,000 feet when the duplication was recognized. The FAA said the aircraft maintained the required separation throughout the incident. The Phoenix air traffic controller quickly recognized the problem and began distinguishing the two aircraft as “American 2482 on the arrival” and “American 2482 on the departure.” The controller then kept the arriving aircraft above the departing aircraft and prevented the departure from climbing into the arrival’s altitude, maintaining vertical separation as their flight paths converged. The controller also alerted both crews to the other aircraft. Reports said the pilots were able to see each other while they were still miles apart, providing an additional layer of awareness as the two aircraft crossed paths. No source has publicly released an exact minimum horizontal distance between the aircraft, and the FAA has confirmed only that required separation was maintained. The incident was captured in air traffic control audio published by ATC.com and subsequently highlighted by media outlets. After the departing aircraft had cleared the area, the controller said, “I’ve been working air traffic for 25 years. I’ve never seen two aircraft pretty much merge with the same call sign. That’s pretty incredible.” The arriving pilot later complimented the controller, saying “nice work.” The controller responded, “It could have been disastrous, but I’m glad it worked out.” The precise passenger and crew numbers aboard the two Boeing 737-800s have not been publicly disclosed by the FAA or American Airlines. Both aircraft completed their flights safely, with no injuries or collision reported. American Airlines said, “The diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed. Both flights continued safely and without incident.” Aviation safety expert Steve Arroyo, a former airline dispatcher and pilot, said the incident likely resulted from an oversight within the airline’s dispatch operation. He told Associated Press that someone should have identified that the two aircraft would be airborne at the same time under identical flight numbers. Arroyo described the event as an example of the aviation system’s ability to recover from an error once it reaches another safety layer. The FAA and American Airlines are investigating how the duplicate callsign was allowed to occur. The investigation will determine how the delayed inbound flight and the replacement outbound aircraft were planned and identified, and why the normal safeguards for avoiding simultaneous use of the same callsign did not prevent the situation.

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

August 17, 2026

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich SEO DES: The crew climbed to 9,000 feet and remained near Munich for two hours; Returned after tail-contact and low-tyre-pressure warnings, with damage SOCIAL: A Vietnam Airlines Boeing 787-9 flying from Munich to Hanoi took an unusually long takeoff roll on Runway 26L on August 15, 2026, before becoming airborne near the runway end. The aircraft reportedly travelled about 120 metres beyond the paved surface, with a tailstrike occurring during the late rotation. After takeoff, the crew climbed to around 9,000 feet and remained near Munich for about two hours before returning to the airport after warnings for tail contact and low tyre pressure. The aircraft sustained tail, landing-gear and tyre damage and could not taxi away after landing. The aircraft carried 271 passengers and 16 crew, all of whom were reported safe with no injuries. German authorities are leading the investigation, with Vietnamese investigators assisting, while the exact cause of the prolonged takeoff remains under investigation. Munich, Germany: A Vietnam Airlines Boeing 787-9 bound for Hanoi took an unusually long takeoff run from Munich Airport on August 15 before finally becoming airborne beyond the normal paved runway area, in an incident that resulted in runway damage, a tail strike and subsequent damage to the aircraft's landing gear. The aircraft later returned to Munich after remaining airborne for about two hours, with no injuries reported among the passengers or crew. The exact reason for the aircraft's prolonged acceleration and extremely late liftoff remains under investigation. The most significant part of the incident occurred during the takeoff roll. Video footage recorded from inside the cabin and from outside the airport shows the 787 accelerating along Runway 26L for an unusually long distance before rotation. Instead of lifting off with substantial runway remaining, the aircraft continued almost to the end of the approximately 4,000-metre runway. Reports based on flight-tracking data indicate that the aircraft reached the runway end area before becoming airborne, with reports putting the excursion beyond the paved surface at roughly 120 metres. The available video is particularly significant because it shows that the issue was not simply a conventional tailstrike during an otherwise normal rotation. The aircraft appears to remain on the ground for an unusually long period, with the runway threshold passing while the aircraft was still accelerating. It eventually rotated at the very end of the runway area, after which a large cloud of dust was visible beneath the rear of the aircraft. The reason for the unusually slow or prolonged takeoff has not been established. Online speculation has included possibilities such as an incorrect takeoff configuration, incorrect thrust or a problem affecting the aircraft's acceleration. However, none of those explanations has been confirmed by Vietnam Airlines or investigators and should not be presented as the cause. Vietnam Airlines has described the event as resulting from a technical issue and said the crew followed safety procedures. The airline has not publicly identified a specific technical failure responsible for the aircraft's unusually long takeoff roll. That distinction is important because the aircraft's subsequent warnings and damage do not, by themselves, establish what caused the initial lack of acceleration. Vietnam's aviation authorities have provided additional information on what happened after the aircraft became airborne. According to the latest reporting on the Civil Aviation Authority of Vietnam's information, warnings indicating tail contact and low tyre pressure were triggered shortly after takeoff. The authorities said the aircraft subsequently returned to Munich, while German authorities led the investigation with Vietnamese investigators assisting. After the aircraft finally lifted off, the crew did not immediately attempt to land. The Boeing 787 climbed to around 9,000 feet and remained in the Munich area for approximately two hours. During that period, the crew assessed the situation and reduced the aircraft's weight before returning to the airport. The tailstrike occurred as the aircraft became airborne after the exceptionally long takeoff run. The rear underside of the aircraft contacted the ground, producing the visible dust plume captured on video. A tailstrike can damage the aircraft's lower aft fuselage, pressure vessel, structural frames, systems, wiring and other components around the tail area. In this case, photographs and video circulating after the incident showed damage around the rear fuselage and the loss or damage of the Boeing 787's tailstrike protection component. The full extent of the structural damage, however, remains subject to technical inspection. The aircraft also sustained landing-gear and tyre damage. Reports indicate that several tyres were damaged or deflated, and footage following the return showed the aircraft unable to taxi away from the runway under its own power. The landing-gear damage also resulted in debris being left on the runway. The aircraft eventually landed back at Munich Airport, using the airport's other runway. Following the landing, the affected aircraft remained on the runway, forcing the closure of the runway and requiring airport authorities to clear debris and deal with the disabled aircraft. Traffic was subsequently handled through the other available runway, causing disruption at the German hub. There were no reported injuries among the passengers or crew. The aircraft was carrying passengers and crew on the Munich-Hanoi service; Vietnam Airlines has reported the total as 271 passengers and 16 crew members. All occupants were reported safe after the aircraft returned to Munich. The incident is now being examined by the relevant German authorities, with Vietnamese aviation investigators assisting. Investigators will need to establish why the Boeing 787 did not achieve the expected acceleration during the takeoff roll, why the aircraft reached the end of the runway area before becoming airborne and whether any technical, operational or performance-related factor contributed to the event.

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich

August 17, 2026

Trawsfynydd, United Kingdom: Two people have died after a light aircraft crashed in a remote area near Trawsfynydd, Gwynedd, North Wales, on August 14, after failing to arrive at Caernarfon Airport as scheduled. North Wales Police said it received reports shortly after midday that the aircraft, which had been travelling from an airfield in England, had not reached its destination. A multi-agency air and ground search was launched, with the aircraft eventually located in a remote area near Trawsfynydd. Both people on board were pronounced dead at the scene. The Air Accidents Investigation Branch (AAIB) has been notified and deployed a team of investigators to the site. The incident came to light shortly after noon when the aircraft failed to arrive at Caernarfon Airport, its scheduled destination. Police and partner agencies then began searching for the missing aircraft from the air and ground. The remote location of the wreckage near Trawsfynydd made the operation challenging, although police have not publicly disclosed the exact crash site. North Wales Police Chief Superintendent Owain Llewellyn said: “This has been a challenging search operation,” while thanking the agencies involved for their professionalism and dedication. Police have not released details of what caused the aircraft to crash, and there is currently no official indication that a mechanical failure, weather conditions, pilot action or any other factor was responsible. The AAIB is now leading the technical investigation, meaning any explanation of the circumstances remains premature. The police said they would support the AAIB investigation “to ensure the circumstances leading to this incident are fully understood.” The two occupants were the only people confirmed to have been on board, and both died at the crash site. Their identities have not yet been released publicly by North Wales Police. No official information has also been released on their ages, nationalities, whether one was the pilot and the other a passenger, or their relationship to each other. Police said specialist officers would support the families and friends of those involved. Chief Superintendent Llewellyn said: “Our thoughts are with the families and friends of those involved in this tragic incident.” The aircraft was travelling from an airfield in England towards Caernarfon Airport in Gwynedd. However, neither North Wales Police nor the media reports available so far have identified the departure airfield. The exact route, flight purpose and planned arrival time have also not been disclosed. Details about the aircraft itself also remain limited. Authorities have described it only as a “light aircraft”. Its manufacturer, model, registration, operator and owner have not been publicly confirmed in the official police statement or the initial media reports reviewed for this report. Until those details are confirmed by the AAIB, police, the aircraft registry or another authoritative source, they should not be attributed to the aircraft involved. The search involved multiple agencies using both air and ground resources before the aircraft was located. The police have praised the emergency agencies involved, but the initial statement does not provide a full list of participating organisations, the number of rescuers deployed, the aircraft or helicopters used in the search, or how long it took to locate the wreckage. Those details may emerge as the investigation and recovery operation progresses. The AAIB has now sent investigators to the scene. Its role is to establish the circumstances and probable cause of the accident and, where appropriate, make safety recommendations. No preliminary findings from the investigation have been publicly released.

Two Dead After Light Aircraft Crashes In Remote Area Of North Wales, AAIB Investigates

August 17, 2026

Bengaluru, India: India is targeting the introduction of electric air taxis by 2028, with Union Civil Aviation Minister Ram Mohan Naidu saying testing of electric vertical take-off and landing (eVTOL) aircraft is expected to accelerate from 2027. The latest development comes as Bengaluru-based Sarla Aviation has secured Design Organisation Approval (DOA) from the Directorate General of Civil Aviation (DGCA), a key regulatory step toward type certification of its indigenous eVTOL aircraft. The approval was handed over to Sarla Aviation at the inauguration of its new Bengaluru headquarters on August 8, 2026. Naidu said India wants to see the aircraft operating by 2028. “By 2028, we want to see these machines fly in India. There is a huge requirement, not only in Bangalore, but Mumbai and Delhi,” he said. He added, “I expect that next year we'll be completely in the testing phase,” while reiterating, “By 2028, we plan to make this happen.” Sarla Aviation has also moved beyond the early prototype stage. On July 1, 2026, the company announced that its half-scale Sylla 1.0 eVTOL technology demonstrator had completed more than 500 tests and over 18 hours of flight testing during a six-month campaign. The 700-kg-class aircraft has a 7.5-metre wingspan and, according to Sarla, became the heaviest electric aircraft to take off in India. The programme tested the aircraft's electric propulsion, battery architecture, distributed propulsion, flight controls, airframe and landing gear as an integrated system. Sarla Aviation CTO and co-founder Rakesh Gaonkar said the Sylla programme had produced the data needed to guide the next stage of development. “Sylla has given us the data we set out to capture, and those learnings are already shaping our next-gen aircraft as we move towards transition and sustained wing-borne flight on our journey to our 6+1 air taxi Shunya,” he said. The next step is Sylla 2.0, which is intended to demonstrate controlled transition from hover to sustained wing-borne flight. That is an important stage before the company moves toward a certifiable passenger-carrying eVTOL. Sarla's planned production aircraft is the six-passenger-plus-pilot Shunya. The developments provide an important update to the electric-air-taxi plan outlined by ET Now. The publication reported that India had set a 2028 target for eVTOL aircraft, with Naidu saying testing would gather pace the following year. The report highlighted Bengaluru, Mumbai and Delhi as cities where demand for such aircraft could be particularly significant because of severe road congestion and lengthy airport-city journeys. An eVTOL is an electrically powered aircraft capable of vertical take-off and landing. Unlike conventional fixed-wing aircraft, it does not require a conventional runway and can potentially operate from smaller facilities closer to urban centres. The technology combines characteristics associated with helicopters, drones and conventional aircraft and is being developed under the broader advanced-air-mobility sector. Sarla Aviation's Shunya is designed around seven electric motors. Six motors provide vertical lift, while a seventh motor mounted at the rear provides forward propulsion. Sarla Aviation co-founder and CEO Adrian Schmidt explained the configuration to ANI: “It's powered by six electric motors that lift it up and one in the rear that pushes it forward. So we have a total of seven electric motors that we're using and it's piloted as of now with six passengers.” The company has said the aircraft's propulsion remains electrically driven. However, Schmidt explained that the design leaves room for a turbo-generator that could potentially recharge the batteries during flight. “We have enough space allocation so that we can consider putting in a turbo generator to charge our batteries mid-flight. But the energy transition from the battery to the motors is always going to be purely electric,” he said. Sarla first unveiled the Shunya prototype at the Bharat Mobility Global Expo in New Delhi in January 2025. The aircraft was presented as a six-passenger eVTOL with a maximum payload of about 680 kg and a targeted top speed of up to 250 km/h. The company said it was designed primarily for short urban journeys of roughly 20–30 km, while reported specifications indicated a potential range of up to 160 km with available battery technology. Sarla's roadmap has also included infrastructure and manufacturing. In November 2025, the company signed an MoU with the Andhra Pradesh government for a 500-acre aerospace campus in Anantapur, with an initial investment of ₹1,300 crore. Sarla described the project as an integrated Urban Air Mobility facility for eVTOL manufacturing and related activities. The company has said the facility is intended to support future aircraft production and air-taxi operations. The company's airport strategy also began taking shape earlier. Sarla Aviation and Bengaluru International Airport Limited signed a partnership agreement in January 2024 to explore an eVTOL ecosystem at Bengaluru airport, including connectivity between the airport and urban areas, vertiport infrastructure and an advanced traffic-management system for future eVTOL operations. Healthcare is another potential application. Bengaluru airport had an agreement with Sarla Aviation for last-mile connectivity and that Manipal Hospitals had also entered an agreement with the company for potential air-ambulance operations. More recent industry reporting indicates that hospitals and air-ambulance operators are increasingly exploring eVTOL partnerships as India develops its advanced-air-mobility ecosystem. The possible uses therefore extend beyond passenger air taxis. The technology could support airport-to-city transfers, last-mile connectivity, air ambulance operations, medical evacuation and cargo transportation. For India, airport connectivity is expected to be one of the earliest practical applications because road journeys between major airports and city centres can take considerable time. Naidu has said an airport-to-city journey that currently takes as long as two hours could potentially be reduced to around 20–30 minutes using eVTOL aircraft. The initial model is therefore expected to focus on short-distance and airport-linked journeys rather than replacing conventional public transportation. The Indian eVTOL market is not limited to Sarla Aviation. Chennai-based The ePlane Company is developing its e200X electric aircraft, while Hyderabad-based BluJ Aerospace is working on eVTOL technology for cargo and other applications. India is therefore developing multiple domestic approaches to advanced air mobility rather than relying solely on one manufacturer. There is also an international dimension to India's air-taxi plans. In 2023, InterGlobe Enterprises, the parent company of IndiGo, announced a partnership with US-based Archer Aviation to explore an all-electric air-taxi service in India, with an original 2026 target. However, that timeline has not materialised as initially envisaged. In 2026, IndiGo Ventures separately invested about ₹10 crore in Sarla Aviation, giving the Indian startup additional strategic backing. Importantly, the IndiGo investment should not be presented as confirmation that IndiGo itself will operate Sarla's eVTOL air-taxi service. Recent reporting said Sarla Aviation clarified that IndiGo's investment did not mean the airline was directly involved in its eVTOL operating plans. The regulatory process remains one of the biggest hurdles. Before commercial passenger operations can begin, eVTOL aircraft must demonstrate compliance with safety and airworthiness requirements and obtain the necessary certification. The DGCA will have to address aircraft design, flight operations, pilot qualifications, infrastructure, vertiports and integration with existing air-traffic systems. Infrastructure is another challenge. Commercial operations will require suitable landing and take-off locations, charging or energy infrastructure, maintenance facilities and systems for managing eVTOL traffic around densely populated areas. Battery performance, aircraft range, weather, operating economics and air-traffic management will also influence whether the 2028 target can be achieved at scale. Sarla's progress in 2026 nevertheless represents a significant shift from the concept and prototype phase. With the Sylla demonstrator having completed an extensive flight-test campaign and the company now holding DGCA Design Organisation Approval, its Shunya programme has entered a more advanced development and certification phase. The government's 2028 target will now depend on the pace of testing, transition-flight development, type certification, infrastructure creation and operational approvals over the next two years.

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

August 16, 2026

Fochville, South Africa: The preliminary accident report, released on 28 July 2026 by the Accident and Incident Investigations Division (AIID) of the South African Civil Aviation Authority (SACAA), found that the engine of a Bird Aviation Piper PA-28-180 registered ZS-ESZ was not producing power when the aircraft struck the ground near Fochville, Gauteng, on 27 June 2026. The report remains preliminary, with the investigation still ongoing and the AIID cautioning that its findings do not apportion blame or liability. According to the report, the operator was Bird Aviation, while the aircraft was being used under a hire-and-fly arrangement for hour-building. The operation was classified as Training under Part 91, and the aircraft belonged to the approved training organisation (ATO) from which it was hired. The accident involved two people, a 21-year-old Indian pilot and one passenger. Both were fatally injured and the aircraft was destroyed. The pilot held a valid Private Pilot Licence (PPL) and was building flight hours toward a Commercial Pilot Licence (CPL) through the ATO. The flight took place on the afternoon of 27 June 2026, when the pilot and passenger departed Lanseria International Airport (FALA) in Gauteng on an hour-building flight, intending to return to the same airport. The flight was conducted under visual meteorological conditions (VMC) and in accordance with Part 91 of the Civil Aviation Regulations. The flight had initially been planned for 0900Z, but departure was delayed because of persistent haze and low visibility. After conditions improved, the aircraft departed Runway 07 at 1325Z, as confirmed by an air traffic control officer at Lanseria. It then flew toward the Johannesburg General Flying Area (GFA), Flight Area Dangerous 182 (FAD 182). Multiple eyewitnesses later reported seeing the aircraft flying unusually low and performing unfamiliar manoeuvres. The aircraft subsequently flipped and began spinning to the left before impacting the ground. The crash occurred on a farm at Elandsfontein, south-east of Fochville, Gauteng, at coordinates 26° 35' 27.30" South, 27° 33' 41.24" East, with a field elevation of 5,124 feet. The accident was recorded at 1415Z. The pilot was a 21-year-old Indian national with a valid PPL. His licence was initially issued by the regulator on 25 May 2026 and was valid until 30 April 2027. His Class 2 aviation medical certificate was issued on 26 March 2025 and was valid until 31 March 2030. The report states that the aircraft type was endorsed on his licence and that he had no previous accidents recorded in relation to the investigation. The pilot had accumulated 132.2 total flight hours, including 19.4 hours in the previous seven days and 55.1 hours in the previous 90 days. He had flown 43.8 hours on the aircraft during the previous 90 days and had accumulated 122.7 hours on the Piper PA-28-180. The aircraft was a 1977-built Piper PA-28-180, a four-seat, single-engine, all-metal, low-wing aircraft with fixed tricycle landing gear. It was powered by a four-cylinder, naturally aspirated 180-horsepower Lycoming O-360-series engine. Its serial number was 28-3303, and it had accumulated 3,242.6 airframe hours by the time of the accident. The AIID found that the aircraft had valid registration and airworthiness documentation. Its current Certificate of Registration had been issued on 19 September 2025, while its latest Certificate of Airworthiness was valid until 31 October 2026. The aircraft underwent its mandatory periodic inspection on 13 March 2026 at 3,218.4 airframe hours, after which a Certificate of Release to Service was issued, valid until 12 March 2027 or 3,318.4 total airframe hours, whichever came first. The aircraft was maintained by an approved aircraft maintenance organisation whose certificate was valid until 30 June 2026. The organisation held Category A and Category C ratings for the aircraft's airframe and engine. The ATO's certificate had been renewed on 17 November 2025 and was valid until 28 February 2029. Fuel records showed that 111 litres of Avgas 100LL had been uplifted after the aircraft's flight on 26 June 2026, with the pilot refuelling the tanks before parking the aircraft. The Piper PA-28-180 has a fuel capacity of 189 litres, providing approximately six hours of endurance. The preliminary findings state that the aircraft departed Lanseria with full fuel tanks and no technical issues. However, fuel was found leaking from the aircraft after the accident. The report does not currently identify the fuel leak as the cause of the engine power loss. Weather conditions were favourable and were not considered a contributing factor. The 1400Z METAR from Lanseria recorded winds from 300° at 7 knots, CAVOK visibility, a temperature of 16°C, scattered clouds at 4,500 feet, a dew point of 5°C and QNH of 1026 hPa. The aircraft's navigation and communication equipment had no recorded defects before the flight. It was not equipped with a flight data recorder (FDR) or cockpit voice recorder (CVR), and the report states that neither was required for this aircraft type. The wreckage examination showed that the aircraft hit the ground in a steep nose-down attitude at high speed with little forward momentum. The debris was concentrated around the impact point, with a crater being the only ground scar identified. The aircraft came to rest facing south-east. Investigators found that the ailerons could not be moved and were both in the down position, while the elevator and rudder moved freely. The landing gear had broken and collapsed rearwards. Both wings suffered severe leading-edge damage and accordion-like deformation that ruptured the fuel tanks. The damage was consistent with heavy compressive loading during the steep, rapid-impact sequence. The top engine cowling had separated from the aircraft and was found approximately 10 metres ahead of the main wreckage. The engine cradle was deformed and the engine was facing slightly to the right. The propeller showed asymmetric damage, with one blade bent rearwards and the other showing little or no deformation. Neither blade displayed S-curve bending. The AIID said the damage pattern was consistent with the propeller being non-rotating at impact. This evidence, together with eyewitness accounts of the pilot apparently attempting to restart the engine, led investigators to conclude that the engine was not producing power at the time of impact. However, the preliminary report does not yet establish the underlying reason for the loss of engine power. The instrument panel was broken into multiple pieces, with several indicators dislodged from their original positions. The report does not provide a final interpretation of the instrument evidence at this stage. There was no evidence of a pre- or post-impact fire. Investigators considered the accident not survivable because of the extent of cockpit damage. Emergency responders reported that the pilot-in-command was not wearing his seat belt and was consequently thrown from the aircraft. Medical and pathological information is reserved for the final report. The aircraft was operating in the Johannesburg GFA within FAD 182, outside the Terminal Control Area. FAD 182 extends from the ground to Flight Level 100, or 10,000 feet, except where it intersects the TMA. Bird Aviation also used the Safely Track Me application to monitor flights. The system relied on the pilot's mobile-phone GPS signal. Tracking was active when ZS-ESZ departed Lanseria, but shortly after the aircraft exited the Johannesburg Special Rules Area West TMA, the phone stopped transmitting its GPS position and the aircraft could no longer be tracked through the application. The AIID's preliminary findings confirm that the pilot was qualified and medically fit for the flight, the aircraft was being used under a valid hire-and-fly arrangement for hour-building, the operator/ATO held a valid certificate, the aircraft had valid registration and airworthiness documentation, and its maintenance records were up to date. The investigation therefore establishes several key facts but has not yet determined the precise cause of the accident. The aircraft left Lanseria with full fuel and no known technical issues; the engine was not producing power at impact; weather was not a factor; and the aircraft entered a steep, high-speed descent before striking the ground. The AIID is continuing to examine other aspects of the accident that could have safety implications. No safety recommendations have been issued at this stage. The AIID said these will be addressed in the final report. The investigation was classified as a Category 1 accident. The AIID appointed an investigator-in-charge and a co-investigator, dispatched investigators to the site and notified the relevant states and organisations under South African regulations and ICAO Annex 13. The AIID will lead the investigation and issue the final report. The AIID has warned that the preliminary report is based on evidence gathered during an ongoing investigation and that information may change if additional evidence emerges. Accordingly, the current finding should be described as the engine not producing power at impact, rather than stating that investigators have already determined the cause of the engine power loss.

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

August 15, 2026

Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 6

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 6

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 5

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 5

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - PART 4

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 4

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Citywide Networks Must Be Designed Around Real Travel Patterns

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 3

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Part 2- Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 2

Leave a Comment

You must be logged in to post a comment.

Follow on Google News

Join WhatsApp Channel

Subscribe to our Newsletter

Email

Recent News

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after two American Airlines Boeing 737-800s were simultaneously operating under the same “American 2482” callsign while flying in opposite directions between Phoenix and Chicago. One aircraft was arriving at Phoenix from Chicago O’Hare International Airport, while another had just departed Phoenix for Chicago. The unusual overlap occurred after the inbound Flight 2482 was delayed by weather, prompting American Airlines to use another aircraft already at Phoenix so passengers waiting for the outbound service could depart on schedule. Because Flight 2482 normally operates as a Chicago-Phoenix round trip using the same flight number, the replacement aircraft also operated under the 2482 identification. The resulting callsign duplication placed both aircraft in the same area of airspace while communicating on the same frequency. Flightradar24 reported that the arriving aircraft was descending through about 11,000 feet while the departing aircraft was climbing toward 9,000 feet when the duplication was recognized. The FAA said the aircraft maintained the required separation throughout the incident. The Phoenix air traffic controller quickly recognized the problem and began distinguishing the two aircraft as “American 2482 on the arrival” and “American 2482 on the departure.” The controller then kept the arriving aircraft above the departing aircraft and prevented the departure from climbing into the arrival’s altitude, maintaining vertical separation as their flight paths converged. The controller also alerted both crews to the other aircraft. Reports said the pilots were able to see each other while they were still miles apart, providing an additional layer of awareness as the two aircraft crossed paths. No source has publicly released an exact minimum horizontal distance between the aircraft, and the FAA has confirmed only that required separation was maintained. The incident was captured in air traffic control audio published by ATC.com and subsequently highlighted by media outlets. After the departing aircraft had cleared the area, the controller said, “I’ve been working air traffic for 25 years. I’ve never seen two aircraft pretty much merge with the same call sign. That’s pretty incredible.” The arriving pilot later complimented the controller, saying “nice work.” The controller responded, “It could have been disastrous, but I’m glad it worked out.” The precise passenger and crew numbers aboard the two Boeing 737-800s have not been publicly disclosed by the FAA or American Airlines. Both aircraft completed their flights safely, with no injuries or collision reported. American Airlines said, “The diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed. Both flights continued safely and without incident.” Aviation safety expert Steve Arroyo, a former airline dispatcher and pilot, said the incident likely resulted from an oversight within the airline’s dispatch operation. He told Associated Press that someone should have identified that the two aircraft would be airborne at the same time under identical flight numbers. Arroyo described the event as an example of the aviation system’s ability to recover from an error once it reaches another safety layer. The FAA and American Airlines are investigating how the duplicate callsign was allowed to occur. The investigation will determine how the delayed inbound flight and the replacement outbound aircraft were planned and identified, and why the normal safeguards for avoiding simultaneous use of the same callsign did not prevent the situation.

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

August 17, 2026

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich SEO DES: The crew climbed to 9,000 feet and remained near Munich for two hours; Returned after tail-contact and low-tyre-pressure warnings, with damage SOCIAL: A Vietnam Airlines Boeing 787-9 flying from Munich to Hanoi took an unusually long takeoff roll on Runway 26L on August 15, 2026, before becoming airborne near the runway end. The aircraft reportedly travelled about 120 metres beyond the paved surface, with a tailstrike occurring during the late rotation. After takeoff, the crew climbed to around 9,000 feet and remained near Munich for about two hours before returning to the airport after warnings for tail contact and low tyre pressure. The aircraft sustained tail, landing-gear and tyre damage and could not taxi away after landing. The aircraft carried 271 passengers and 16 crew, all of whom were reported safe with no injuries. German authorities are leading the investigation, with Vietnamese investigators assisting, while the exact cause of the prolonged takeoff remains under investigation. Munich, Germany: A Vietnam Airlines Boeing 787-9 bound for Hanoi took an unusually long takeoff run from Munich Airport on August 15 before finally becoming airborne beyond the normal paved runway area, in an incident that resulted in runway damage, a tail strike and subsequent damage to the aircraft's landing gear. The aircraft later returned to Munich after remaining airborne for about two hours, with no injuries reported among the passengers or crew. The exact reason for the aircraft's prolonged acceleration and extremely late liftoff remains under investigation. The most significant part of the incident occurred during the takeoff roll. Video footage recorded from inside the cabin and from outside the airport shows the 787 accelerating along Runway 26L for an unusually long distance before rotation. Instead of lifting off with substantial runway remaining, the aircraft continued almost to the end of the approximately 4,000-metre runway. Reports based on flight-tracking data indicate that the aircraft reached the runway end area before becoming airborne, with reports putting the excursion beyond the paved surface at roughly 120 metres. The available video is particularly significant because it shows that the issue was not simply a conventional tailstrike during an otherwise normal rotation. The aircraft appears to remain on the ground for an unusually long period, with the runway threshold passing while the aircraft was still accelerating. It eventually rotated at the very end of the runway area, after which a large cloud of dust was visible beneath the rear of the aircraft. The reason for the unusually slow or prolonged takeoff has not been established. Online speculation has included possibilities such as an incorrect takeoff configuration, incorrect thrust or a problem affecting the aircraft's acceleration. However, none of those explanations has been confirmed by Vietnam Airlines or investigators and should not be presented as the cause. Vietnam Airlines has described the event as resulting from a technical issue and said the crew followed safety procedures. The airline has not publicly identified a specific technical failure responsible for the aircraft's unusually long takeoff roll. That distinction is important because the aircraft's subsequent warnings and damage do not, by themselves, establish what caused the initial lack of acceleration. Vietnam's aviation authorities have provided additional information on what happened after the aircraft became airborne. According to the latest reporting on the Civil Aviation Authority of Vietnam's information, warnings indicating tail contact and low tyre pressure were triggered shortly after takeoff. The authorities said the aircraft subsequently returned to Munich, while German authorities led the investigation with Vietnamese investigators assisting. After the aircraft finally lifted off, the crew did not immediately attempt to land. The Boeing 787 climbed to around 9,000 feet and remained in the Munich area for approximately two hours. During that period, the crew assessed the situation and reduced the aircraft's weight before returning to the airport. The tailstrike occurred as the aircraft became airborne after the exceptionally long takeoff run. The rear underside of the aircraft contacted the ground, producing the visible dust plume captured on video. A tailstrike can damage the aircraft's lower aft fuselage, pressure vessel, structural frames, systems, wiring and other components around the tail area. In this case, photographs and video circulating after the incident showed damage around the rear fuselage and the loss or damage of the Boeing 787's tailstrike protection component. The full extent of the structural damage, however, remains subject to technical inspection. The aircraft also sustained landing-gear and tyre damage. Reports indicate that several tyres were damaged or deflated, and footage following the return showed the aircraft unable to taxi away from the runway under its own power. The landing-gear damage also resulted in debris being left on the runway. The aircraft eventually landed back at Munich Airport, using the airport's other runway. Following the landing, the affected aircraft remained on the runway, forcing the closure of the runway and requiring airport authorities to clear debris and deal with the disabled aircraft. Traffic was subsequently handled through the other available runway, causing disruption at the German hub. There were no reported injuries among the passengers or crew. The aircraft was carrying passengers and crew on the Munich-Hanoi service; Vietnam Airlines has reported the total as 271 passengers and 16 crew members. All occupants were reported safe after the aircraft returned to Munich. The incident is now being examined by the relevant German authorities, with Vietnamese aviation investigators assisting. Investigators will need to establish why the Boeing 787 did not achieve the expected acceleration during the takeoff roll, why the aircraft reached the end of the runway area before becoming airborne and whether any technical, operational or performance-related factor contributed to the event.

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich

August 17, 2026

Trawsfynydd, United Kingdom: Two people have died after a light aircraft crashed in a remote area near Trawsfynydd, Gwynedd, North Wales, on August 14, after failing to arrive at Caernarfon Airport as scheduled. North Wales Police said it received reports shortly after midday that the aircraft, which had been travelling from an airfield in England, had not reached its destination. A multi-agency air and ground search was launched, with the aircraft eventually located in a remote area near Trawsfynydd. Both people on board were pronounced dead at the scene. The Air Accidents Investigation Branch (AAIB) has been notified and deployed a team of investigators to the site. The incident came to light shortly after noon when the aircraft failed to arrive at Caernarfon Airport, its scheduled destination. Police and partner agencies then began searching for the missing aircraft from the air and ground. The remote location of the wreckage near Trawsfynydd made the operation challenging, although police have not publicly disclosed the exact crash site. North Wales Police Chief Superintendent Owain Llewellyn said: “This has been a challenging search operation,” while thanking the agencies involved for their professionalism and dedication. Police have not released details of what caused the aircraft to crash, and there is currently no official indication that a mechanical failure, weather conditions, pilot action or any other factor was responsible. The AAIB is now leading the technical investigation, meaning any explanation of the circumstances remains premature. The police said they would support the AAIB investigation “to ensure the circumstances leading to this incident are fully understood.” The two occupants were the only people confirmed to have been on board, and both died at the crash site. Their identities have not yet been released publicly by North Wales Police. No official information has also been released on their ages, nationalities, whether one was the pilot and the other a passenger, or their relationship to each other. Police said specialist officers would support the families and friends of those involved. Chief Superintendent Llewellyn said: “Our thoughts are with the families and friends of those involved in this tragic incident.” The aircraft was travelling from an airfield in England towards Caernarfon Airport in Gwynedd. However, neither North Wales Police nor the media reports available so far have identified the departure airfield. The exact route, flight purpose and planned arrival time have also not been disclosed. Details about the aircraft itself also remain limited. Authorities have described it only as a “light aircraft”. Its manufacturer, model, registration, operator and owner have not been publicly confirmed in the official police statement or the initial media reports reviewed for this report. Until those details are confirmed by the AAIB, police, the aircraft registry or another authoritative source, they should not be attributed to the aircraft involved. The search involved multiple agencies using both air and ground resources before the aircraft was located. The police have praised the emergency agencies involved, but the initial statement does not provide a full list of participating organisations, the number of rescuers deployed, the aircraft or helicopters used in the search, or how long it took to locate the wreckage. Those details may emerge as the investigation and recovery operation progresses. The AAIB has now sent investigators to the scene. Its role is to establish the circumstances and probable cause of the accident and, where appropriate, make safety recommendations. No preliminary findings from the investigation have been publicly released.

Two Dead After Light Aircraft Crashes In Remote Area Of North Wales, AAIB Investigates

August 17, 2026

Bengaluru, India: India is targeting the introduction of electric air taxis by 2028, with Union Civil Aviation Minister Ram Mohan Naidu saying testing of electric vertical take-off and landing (eVTOL) aircraft is expected to accelerate from 2027. The latest development comes as Bengaluru-based Sarla Aviation has secured Design Organisation Approval (DOA) from the Directorate General of Civil Aviation (DGCA), a key regulatory step toward type certification of its indigenous eVTOL aircraft. The approval was handed over to Sarla Aviation at the inauguration of its new Bengaluru headquarters on August 8, 2026. Naidu said India wants to see the aircraft operating by 2028. “By 2028, we want to see these machines fly in India. There is a huge requirement, not only in Bangalore, but Mumbai and Delhi,” he said. He added, “I expect that next year we'll be completely in the testing phase,” while reiterating, “By 2028, we plan to make this happen.” Sarla Aviation has also moved beyond the early prototype stage. On July 1, 2026, the company announced that its half-scale Sylla 1.0 eVTOL technology demonstrator had completed more than 500 tests and over 18 hours of flight testing during a six-month campaign. The 700-kg-class aircraft has a 7.5-metre wingspan and, according to Sarla, became the heaviest electric aircraft to take off in India. The programme tested the aircraft's electric propulsion, battery architecture, distributed propulsion, flight controls, airframe and landing gear as an integrated system. Sarla Aviation CTO and co-founder Rakesh Gaonkar said the Sylla programme had produced the data needed to guide the next stage of development. “Sylla has given us the data we set out to capture, and those learnings are already shaping our next-gen aircraft as we move towards transition and sustained wing-borne flight on our journey to our 6+1 air taxi Shunya,” he said. The next step is Sylla 2.0, which is intended to demonstrate controlled transition from hover to sustained wing-borne flight. That is an important stage before the company moves toward a certifiable passenger-carrying eVTOL. Sarla's planned production aircraft is the six-passenger-plus-pilot Shunya. The developments provide an important update to the electric-air-taxi plan outlined by ET Now. The publication reported that India had set a 2028 target for eVTOL aircraft, with Naidu saying testing would gather pace the following year. The report highlighted Bengaluru, Mumbai and Delhi as cities where demand for such aircraft could be particularly significant because of severe road congestion and lengthy airport-city journeys. An eVTOL is an electrically powered aircraft capable of vertical take-off and landing. Unlike conventional fixed-wing aircraft, it does not require a conventional runway and can potentially operate from smaller facilities closer to urban centres. The technology combines characteristics associated with helicopters, drones and conventional aircraft and is being developed under the broader advanced-air-mobility sector. Sarla Aviation's Shunya is designed around seven electric motors. Six motors provide vertical lift, while a seventh motor mounted at the rear provides forward propulsion. Sarla Aviation co-founder and CEO Adrian Schmidt explained the configuration to ANI: “It's powered by six electric motors that lift it up and one in the rear that pushes it forward. So we have a total of seven electric motors that we're using and it's piloted as of now with six passengers.” The company has said the aircraft's propulsion remains electrically driven. However, Schmidt explained that the design leaves room for a turbo-generator that could potentially recharge the batteries during flight. “We have enough space allocation so that we can consider putting in a turbo generator to charge our batteries mid-flight. But the energy transition from the battery to the motors is always going to be purely electric,” he said. Sarla first unveiled the Shunya prototype at the Bharat Mobility Global Expo in New Delhi in January 2025. The aircraft was presented as a six-passenger eVTOL with a maximum payload of about 680 kg and a targeted top speed of up to 250 km/h. The company said it was designed primarily for short urban journeys of roughly 20–30 km, while reported specifications indicated a potential range of up to 160 km with available battery technology. Sarla's roadmap has also included infrastructure and manufacturing. In November 2025, the company signed an MoU with the Andhra Pradesh government for a 500-acre aerospace campus in Anantapur, with an initial investment of ₹1,300 crore. Sarla described the project as an integrated Urban Air Mobility facility for eVTOL manufacturing and related activities. The company has said the facility is intended to support future aircraft production and air-taxi operations. The company's airport strategy also began taking shape earlier. Sarla Aviation and Bengaluru International Airport Limited signed a partnership agreement in January 2024 to explore an eVTOL ecosystem at Bengaluru airport, including connectivity between the airport and urban areas, vertiport infrastructure and an advanced traffic-management system for future eVTOL operations. Healthcare is another potential application. Bengaluru airport had an agreement with Sarla Aviation for last-mile connectivity and that Manipal Hospitals had also entered an agreement with the company for potential air-ambulance operations. More recent industry reporting indicates that hospitals and air-ambulance operators are increasingly exploring eVTOL partnerships as India develops its advanced-air-mobility ecosystem. The possible uses therefore extend beyond passenger air taxis. The technology could support airport-to-city transfers, last-mile connectivity, air ambulance operations, medical evacuation and cargo transportation. For India, airport connectivity is expected to be one of the earliest practical applications because road journeys between major airports and city centres can take considerable time. Naidu has said an airport-to-city journey that currently takes as long as two hours could potentially be reduced to around 20–30 minutes using eVTOL aircraft. The initial model is therefore expected to focus on short-distance and airport-linked journeys rather than replacing conventional public transportation. The Indian eVTOL market is not limited to Sarla Aviation. Chennai-based The ePlane Company is developing its e200X electric aircraft, while Hyderabad-based BluJ Aerospace is working on eVTOL technology for cargo and other applications. India is therefore developing multiple domestic approaches to advanced air mobility rather than relying solely on one manufacturer. There is also an international dimension to India's air-taxi plans. In 2023, InterGlobe Enterprises, the parent company of IndiGo, announced a partnership with US-based Archer Aviation to explore an all-electric air-taxi service in India, with an original 2026 target. However, that timeline has not materialised as initially envisaged. In 2026, IndiGo Ventures separately invested about ₹10 crore in Sarla Aviation, giving the Indian startup additional strategic backing. Importantly, the IndiGo investment should not be presented as confirmation that IndiGo itself will operate Sarla's eVTOL air-taxi service. Recent reporting said Sarla Aviation clarified that IndiGo's investment did not mean the airline was directly involved in its eVTOL operating plans. The regulatory process remains one of the biggest hurdles. Before commercial passenger operations can begin, eVTOL aircraft must demonstrate compliance with safety and airworthiness requirements and obtain the necessary certification. The DGCA will have to address aircraft design, flight operations, pilot qualifications, infrastructure, vertiports and integration with existing air-traffic systems. Infrastructure is another challenge. Commercial operations will require suitable landing and take-off locations, charging or energy infrastructure, maintenance facilities and systems for managing eVTOL traffic around densely populated areas. Battery performance, aircraft range, weather, operating economics and air-traffic management will also influence whether the 2028 target can be achieved at scale. Sarla's progress in 2026 nevertheless represents a significant shift from the concept and prototype phase. With the Sylla demonstrator having completed an extensive flight-test campaign and the company now holding DGCA Design Organisation Approval, its Shunya programme has entered a more advanced development and certification phase. The government's 2028 target will now depend on the pace of testing, transition-flight development, type certification, infrastructure creation and operational approvals over the next two years.

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

August 16, 2026

Fochville, South Africa: The preliminary accident report, released on 28 July 2026 by the Accident and Incident Investigations Division (AIID) of the South African Civil Aviation Authority (SACAA), found that the engine of a Bird Aviation Piper PA-28-180 registered ZS-ESZ was not producing power when the aircraft struck the ground near Fochville, Gauteng, on 27 June 2026. The report remains preliminary, with the investigation still ongoing and the AIID cautioning that its findings do not apportion blame or liability. According to the report, the operator was Bird Aviation, while the aircraft was being used under a hire-and-fly arrangement for hour-building. The operation was classified as Training under Part 91, and the aircraft belonged to the approved training organisation (ATO) from which it was hired. The accident involved two people, a 21-year-old Indian pilot and one passenger. Both were fatally injured and the aircraft was destroyed. The pilot held a valid Private Pilot Licence (PPL) and was building flight hours toward a Commercial Pilot Licence (CPL) through the ATO. The flight took place on the afternoon of 27 June 2026, when the pilot and passenger departed Lanseria International Airport (FALA) in Gauteng on an hour-building flight, intending to return to the same airport. The flight was conducted under visual meteorological conditions (VMC) and in accordance with Part 91 of the Civil Aviation Regulations. The flight had initially been planned for 0900Z, but departure was delayed because of persistent haze and low visibility. After conditions improved, the aircraft departed Runway 07 at 1325Z, as confirmed by an air traffic control officer at Lanseria. It then flew toward the Johannesburg General Flying Area (GFA), Flight Area Dangerous 182 (FAD 182). Multiple eyewitnesses later reported seeing the aircraft flying unusually low and performing unfamiliar manoeuvres. The aircraft subsequently flipped and began spinning to the left before impacting the ground. The crash occurred on a farm at Elandsfontein, south-east of Fochville, Gauteng, at coordinates 26° 35' 27.30" South, 27° 33' 41.24" East, with a field elevation of 5,124 feet. The accident was recorded at 1415Z. The pilot was a 21-year-old Indian national with a valid PPL. His licence was initially issued by the regulator on 25 May 2026 and was valid until 30 April 2027. His Class 2 aviation medical certificate was issued on 26 March 2025 and was valid until 31 March 2030. The report states that the aircraft type was endorsed on his licence and that he had no previous accidents recorded in relation to the investigation. The pilot had accumulated 132.2 total flight hours, including 19.4 hours in the previous seven days and 55.1 hours in the previous 90 days. He had flown 43.8 hours on the aircraft during the previous 90 days and had accumulated 122.7 hours on the Piper PA-28-180. The aircraft was a 1977-built Piper PA-28-180, a four-seat, single-engine, all-metal, low-wing aircraft with fixed tricycle landing gear. It was powered by a four-cylinder, naturally aspirated 180-horsepower Lycoming O-360-series engine. Its serial number was 28-3303, and it had accumulated 3,242.6 airframe hours by the time of the accident. The AIID found that the aircraft had valid registration and airworthiness documentation. Its current Certificate of Registration had been issued on 19 September 2025, while its latest Certificate of Airworthiness was valid until 31 October 2026. The aircraft underwent its mandatory periodic inspection on 13 March 2026 at 3,218.4 airframe hours, after which a Certificate of Release to Service was issued, valid until 12 March 2027 or 3,318.4 total airframe hours, whichever came first. The aircraft was maintained by an approved aircraft maintenance organisation whose certificate was valid until 30 June 2026. The organisation held Category A and Category C ratings for the aircraft's airframe and engine. The ATO's certificate had been renewed on 17 November 2025 and was valid until 28 February 2029. Fuel records showed that 111 litres of Avgas 100LL had been uplifted after the aircraft's flight on 26 June 2026, with the pilot refuelling the tanks before parking the aircraft. The Piper PA-28-180 has a fuel capacity of 189 litres, providing approximately six hours of endurance. The preliminary findings state that the aircraft departed Lanseria with full fuel tanks and no technical issues. However, fuel was found leaking from the aircraft after the accident. The report does not currently identify the fuel leak as the cause of the engine power loss. Weather conditions were favourable and were not considered a contributing factor. The 1400Z METAR from Lanseria recorded winds from 300° at 7 knots, CAVOK visibility, a temperature of 16°C, scattered clouds at 4,500 feet, a dew point of 5°C and QNH of 1026 hPa. The aircraft's navigation and communication equipment had no recorded defects before the flight. It was not equipped with a flight data recorder (FDR) or cockpit voice recorder (CVR), and the report states that neither was required for this aircraft type. The wreckage examination showed that the aircraft hit the ground in a steep nose-down attitude at high speed with little forward momentum. The debris was concentrated around the impact point, with a crater being the only ground scar identified. The aircraft came to rest facing south-east. Investigators found that the ailerons could not be moved and were both in the down position, while the elevator and rudder moved freely. The landing gear had broken and collapsed rearwards. Both wings suffered severe leading-edge damage and accordion-like deformation that ruptured the fuel tanks. The damage was consistent with heavy compressive loading during the steep, rapid-impact sequence. The top engine cowling had separated from the aircraft and was found approximately 10 metres ahead of the main wreckage. The engine cradle was deformed and the engine was facing slightly to the right. The propeller showed asymmetric damage, with one blade bent rearwards and the other showing little or no deformation. Neither blade displayed S-curve bending. The AIID said the damage pattern was consistent with the propeller being non-rotating at impact. This evidence, together with eyewitness accounts of the pilot apparently attempting to restart the engine, led investigators to conclude that the engine was not producing power at the time of impact. However, the preliminary report does not yet establish the underlying reason for the loss of engine power. The instrument panel was broken into multiple pieces, with several indicators dislodged from their original positions. The report does not provide a final interpretation of the instrument evidence at this stage. There was no evidence of a pre- or post-impact fire. Investigators considered the accident not survivable because of the extent of cockpit damage. Emergency responders reported that the pilot-in-command was not wearing his seat belt and was consequently thrown from the aircraft. Medical and pathological information is reserved for the final report. The aircraft was operating in the Johannesburg GFA within FAD 182, outside the Terminal Control Area. FAD 182 extends from the ground to Flight Level 100, or 10,000 feet, except where it intersects the TMA. Bird Aviation also used the Safely Track Me application to monitor flights. The system relied on the pilot's mobile-phone GPS signal. Tracking was active when ZS-ESZ departed Lanseria, but shortly after the aircraft exited the Johannesburg Special Rules Area West TMA, the phone stopped transmitting its GPS position and the aircraft could no longer be tracked through the application. The AIID's preliminary findings confirm that the pilot was qualified and medically fit for the flight, the aircraft was being used under a valid hire-and-fly arrangement for hour-building, the operator/ATO held a valid certificate, the aircraft had valid registration and airworthiness documentation, and its maintenance records were up to date. The investigation therefore establishes several key facts but has not yet determined the precise cause of the accident. The aircraft left Lanseria with full fuel and no known technical issues; the engine was not producing power at impact; weather was not a factor; and the aircraft entered a steep, high-speed descent before striking the ground. The AIID is continuing to examine other aspects of the accident that could have safety implications. No safety recommendations have been issued at this stage. The AIID said these will be addressed in the final report. The investigation was classified as a Category 1 accident. The AIID appointed an investigator-in-charge and a co-investigator, dispatched investigators to the site and notified the relevant states and organisations under South African regulations and ICAO Annex 13. The AIID will lead the investigation and issue the final report. The AIID has warned that the preliminary report is based on evidence gathered during an ongoing investigation and that information may change if additional evidence emerges. Accordingly, the current finding should be described as the engine not producing power at impact, rather than stating that investigators have already determined the cause of the engine power loss.

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

August 15, 2026

Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 6

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 6

July 25, 2026

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 5

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 5

July 23, 2026

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - PART 4

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 4

July 21, 2026

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Citywide Networks Must Be Designed Around Real Travel Patterns

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 3

July 19, 2026

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Part 2- Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 2

July 17, 2026

Follow on Google News

Join WhatsApp Channel

Subscribe to our Newsletter

Email

Recent News

Phoenix, United States: A potential mid-air collision was averted near Phoenix Sky Harbor International Airport on August 14, 2026, after two American Airlines Boeing 737-800s were simultaneously operating under the same “American 2482” callsign while flying in opposite directions between Phoenix and Chicago. One aircraft was arriving at Phoenix from Chicago O’Hare International Airport, while another had just departed Phoenix for Chicago. The unusual overlap occurred after the inbound Flight 2482 was delayed by weather, prompting American Airlines to use another aircraft already at Phoenix so passengers waiting for the outbound service could depart on schedule. Because Flight 2482 normally operates as a Chicago-Phoenix round trip using the same flight number, the replacement aircraft also operated under the 2482 identification. The resulting callsign duplication placed both aircraft in the same area of airspace while communicating on the same frequency. Flightradar24 reported that the arriving aircraft was descending through about 11,000 feet while the departing aircraft was climbing toward 9,000 feet when the duplication was recognized. The FAA said the aircraft maintained the required separation throughout the incident. The Phoenix air traffic controller quickly recognized the problem and began distinguishing the two aircraft as “American 2482 on the arrival” and “American 2482 on the departure.” The controller then kept the arriving aircraft above the departing aircraft and prevented the departure from climbing into the arrival’s altitude, maintaining vertical separation as their flight paths converged. The controller also alerted both crews to the other aircraft. Reports said the pilots were able to see each other while they were still miles apart, providing an additional layer of awareness as the two aircraft crossed paths. No source has publicly released an exact minimum horizontal distance between the aircraft, and the FAA has confirmed only that required separation was maintained. The incident was captured in air traffic control audio published by ATC.com and subsequently highlighted by media outlets. After the departing aircraft had cleared the area, the controller said, “I’ve been working air traffic for 25 years. I’ve never seen two aircraft pretty much merge with the same call sign. That’s pretty incredible.” The arriving pilot later complimented the controller, saying “nice work.” The controller responded, “It could have been disastrous, but I’m glad it worked out.” The precise passenger and crew numbers aboard the two Boeing 737-800s have not been publicly disclosed by the FAA or American Airlines. Both aircraft completed their flights safely, with no injuries or collision reported. American Airlines said, “The diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed. Both flights continued safely and without incident.” Aviation safety expert Steve Arroyo, a former airline dispatcher and pilot, said the incident likely resulted from an oversight within the airline’s dispatch operation. He told Associated Press that someone should have identified that the two aircraft would be airborne at the same time under identical flight numbers. Arroyo described the event as an example of the aviation system’s ability to recover from an error once it reaches another safety layer. The FAA and American Airlines are investigating how the duplicate callsign was allowed to occur. The investigation will determine how the delayed inbound flight and the replacement outbound aircraft were planned and identified, and why the normal safeguards for avoiding simultaneous use of the same callsign did not prevent the situation.

Two American Airlines Jets Sharing Same Callsign Avoid Near-Midair Collision In Phoenix

August 17, 2026

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich SEO DES: The crew climbed to 9,000 feet and remained near Munich for two hours; Returned after tail-contact and low-tyre-pressure warnings, with damage SOCIAL: A Vietnam Airlines Boeing 787-9 flying from Munich to Hanoi took an unusually long takeoff roll on Runway 26L on August 15, 2026, before becoming airborne near the runway end. The aircraft reportedly travelled about 120 metres beyond the paved surface, with a tailstrike occurring during the late rotation. After takeoff, the crew climbed to around 9,000 feet and remained near Munich for about two hours before returning to the airport after warnings for tail contact and low tyre pressure. The aircraft sustained tail, landing-gear and tyre damage and could not taxi away after landing. The aircraft carried 271 passengers and 16 crew, all of whom were reported safe with no injuries. German authorities are leading the investigation, with Vietnamese investigators assisting, while the exact cause of the prolonged takeoff remains under investigation. Munich, Germany: A Vietnam Airlines Boeing 787-9 bound for Hanoi took an unusually long takeoff run from Munich Airport on August 15 before finally becoming airborne beyond the normal paved runway area, in an incident that resulted in runway damage, a tail strike and subsequent damage to the aircraft's landing gear. The aircraft later returned to Munich after remaining airborne for about two hours, with no injuries reported among the passengers or crew. The exact reason for the aircraft's prolonged acceleration and extremely late liftoff remains under investigation. The most significant part of the incident occurred during the takeoff roll. Video footage recorded from inside the cabin and from outside the airport shows the 787 accelerating along Runway 26L for an unusually long distance before rotation. Instead of lifting off with substantial runway remaining, the aircraft continued almost to the end of the approximately 4,000-metre runway. Reports based on flight-tracking data indicate that the aircraft reached the runway end area before becoming airborne, with reports putting the excursion beyond the paved surface at roughly 120 metres. The available video is particularly significant because it shows that the issue was not simply a conventional tailstrike during an otherwise normal rotation. The aircraft appears to remain on the ground for an unusually long period, with the runway threshold passing while the aircraft was still accelerating. It eventually rotated at the very end of the runway area, after which a large cloud of dust was visible beneath the rear of the aircraft. The reason for the unusually slow or prolonged takeoff has not been established. Online speculation has included possibilities such as an incorrect takeoff configuration, incorrect thrust or a problem affecting the aircraft's acceleration. However, none of those explanations has been confirmed by Vietnam Airlines or investigators and should not be presented as the cause. Vietnam Airlines has described the event as resulting from a technical issue and said the crew followed safety procedures. The airline has not publicly identified a specific technical failure responsible for the aircraft's unusually long takeoff roll. That distinction is important because the aircraft's subsequent warnings and damage do not, by themselves, establish what caused the initial lack of acceleration. Vietnam's aviation authorities have provided additional information on what happened after the aircraft became airborne. According to the latest reporting on the Civil Aviation Authority of Vietnam's information, warnings indicating tail contact and low tyre pressure were triggered shortly after takeoff. The authorities said the aircraft subsequently returned to Munich, while German authorities led the investigation with Vietnamese investigators assisting. After the aircraft finally lifted off, the crew did not immediately attempt to land. The Boeing 787 climbed to around 9,000 feet and remained in the Munich area for approximately two hours. During that period, the crew assessed the situation and reduced the aircraft's weight before returning to the airport. The tailstrike occurred as the aircraft became airborne after the exceptionally long takeoff run. The rear underside of the aircraft contacted the ground, producing the visible dust plume captured on video. A tailstrike can damage the aircraft's lower aft fuselage, pressure vessel, structural frames, systems, wiring and other components around the tail area. In this case, photographs and video circulating after the incident showed damage around the rear fuselage and the loss or damage of the Boeing 787's tailstrike protection component. The full extent of the structural damage, however, remains subject to technical inspection. The aircraft also sustained landing-gear and tyre damage. Reports indicate that several tyres were damaged or deflated, and footage following the return showed the aircraft unable to taxi away from the runway under its own power. The landing-gear damage also resulted in debris being left on the runway. The aircraft eventually landed back at Munich Airport, using the airport's other runway. Following the landing, the affected aircraft remained on the runway, forcing the closure of the runway and requiring airport authorities to clear debris and deal with the disabled aircraft. Traffic was subsequently handled through the other available runway, causing disruption at the German hub. There were no reported injuries among the passengers or crew. The aircraft was carrying passengers and crew on the Munich-Hanoi service; Vietnam Airlines has reported the total as 271 passengers and 16 crew members. All occupants were reported safe after the aircraft returned to Munich. The incident is now being examined by the relevant German authorities, with Vietnamese aviation investigators assisting. Investigators will need to establish why the Boeing 787 did not achieve the expected acceleration during the takeoff roll, why the aircraft reached the end of the runway area before becoming airborne and whether any technical, operational or performance-related factor contributed to the event.

Vietnam Airlines Boeing 787 Suffers Tailstrike After Extended Takeoff Run At Munich

August 17, 2026

Trawsfynydd, United Kingdom: Two people have died after a light aircraft crashed in a remote area near Trawsfynydd, Gwynedd, North Wales, on August 14, after failing to arrive at Caernarfon Airport as scheduled. North Wales Police said it received reports shortly after midday that the aircraft, which had been travelling from an airfield in England, had not reached its destination. A multi-agency air and ground search was launched, with the aircraft eventually located in a remote area near Trawsfynydd. Both people on board were pronounced dead at the scene. The Air Accidents Investigation Branch (AAIB) has been notified and deployed a team of investigators to the site. The incident came to light shortly after noon when the aircraft failed to arrive at Caernarfon Airport, its scheduled destination. Police and partner agencies then began searching for the missing aircraft from the air and ground. The remote location of the wreckage near Trawsfynydd made the operation challenging, although police have not publicly disclosed the exact crash site. North Wales Police Chief Superintendent Owain Llewellyn said: “This has been a challenging search operation,” while thanking the agencies involved for their professionalism and dedication. Police have not released details of what caused the aircraft to crash, and there is currently no official indication that a mechanical failure, weather conditions, pilot action or any other factor was responsible. The AAIB is now leading the technical investigation, meaning any explanation of the circumstances remains premature. The police said they would support the AAIB investigation “to ensure the circumstances leading to this incident are fully understood.” The two occupants were the only people confirmed to have been on board, and both died at the crash site. Their identities have not yet been released publicly by North Wales Police. No official information has also been released on their ages, nationalities, whether one was the pilot and the other a passenger, or their relationship to each other. Police said specialist officers would support the families and friends of those involved. Chief Superintendent Llewellyn said: “Our thoughts are with the families and friends of those involved in this tragic incident.” The aircraft was travelling from an airfield in England towards Caernarfon Airport in Gwynedd. However, neither North Wales Police nor the media reports available so far have identified the departure airfield. The exact route, flight purpose and planned arrival time have also not been disclosed. Details about the aircraft itself also remain limited. Authorities have described it only as a “light aircraft”. Its manufacturer, model, registration, operator and owner have not been publicly confirmed in the official police statement or the initial media reports reviewed for this report. Until those details are confirmed by the AAIB, police, the aircraft registry or another authoritative source, they should not be attributed to the aircraft involved. The search involved multiple agencies using both air and ground resources before the aircraft was located. The police have praised the emergency agencies involved, but the initial statement does not provide a full list of participating organisations, the number of rescuers deployed, the aircraft or helicopters used in the search, or how long it took to locate the wreckage. Those details may emerge as the investigation and recovery operation progresses. The AAIB has now sent investigators to the scene. Its role is to establish the circumstances and probable cause of the accident and, where appropriate, make safety recommendations. No preliminary findings from the investigation have been publicly released.

Two Dead After Light Aircraft Crashes In Remote Area Of North Wales, AAIB Investigates

August 17, 2026

Bengaluru, India: India is targeting the introduction of electric air taxis by 2028, with Union Civil Aviation Minister Ram Mohan Naidu saying testing of electric vertical take-off and landing (eVTOL) aircraft is expected to accelerate from 2027. The latest development comes as Bengaluru-based Sarla Aviation has secured Design Organisation Approval (DOA) from the Directorate General of Civil Aviation (DGCA), a key regulatory step toward type certification of its indigenous eVTOL aircraft. The approval was handed over to Sarla Aviation at the inauguration of its new Bengaluru headquarters on August 8, 2026. Naidu said India wants to see the aircraft operating by 2028. “By 2028, we want to see these machines fly in India. There is a huge requirement, not only in Bangalore, but Mumbai and Delhi,” he said. He added, “I expect that next year we'll be completely in the testing phase,” while reiterating, “By 2028, we plan to make this happen.” Sarla Aviation has also moved beyond the early prototype stage. On July 1, 2026, the company announced that its half-scale Sylla 1.0 eVTOL technology demonstrator had completed more than 500 tests and over 18 hours of flight testing during a six-month campaign. The 700-kg-class aircraft has a 7.5-metre wingspan and, according to Sarla, became the heaviest electric aircraft to take off in India. The programme tested the aircraft's electric propulsion, battery architecture, distributed propulsion, flight controls, airframe and landing gear as an integrated system. Sarla Aviation CTO and co-founder Rakesh Gaonkar said the Sylla programme had produced the data needed to guide the next stage of development. “Sylla has given us the data we set out to capture, and those learnings are already shaping our next-gen aircraft as we move towards transition and sustained wing-borne flight on our journey to our 6+1 air taxi Shunya,” he said. The next step is Sylla 2.0, which is intended to demonstrate controlled transition from hover to sustained wing-borne flight. That is an important stage before the company moves toward a certifiable passenger-carrying eVTOL. Sarla's planned production aircraft is the six-passenger-plus-pilot Shunya. The developments provide an important update to the electric-air-taxi plan outlined by ET Now. The publication reported that India had set a 2028 target for eVTOL aircraft, with Naidu saying testing would gather pace the following year. The report highlighted Bengaluru, Mumbai and Delhi as cities where demand for such aircraft could be particularly significant because of severe road congestion and lengthy airport-city journeys. An eVTOL is an electrically powered aircraft capable of vertical take-off and landing. Unlike conventional fixed-wing aircraft, it does not require a conventional runway and can potentially operate from smaller facilities closer to urban centres. The technology combines characteristics associated with helicopters, drones and conventional aircraft and is being developed under the broader advanced-air-mobility sector. Sarla Aviation's Shunya is designed around seven electric motors. Six motors provide vertical lift, while a seventh motor mounted at the rear provides forward propulsion. Sarla Aviation co-founder and CEO Adrian Schmidt explained the configuration to ANI: “It's powered by six electric motors that lift it up and one in the rear that pushes it forward. So we have a total of seven electric motors that we're using and it's piloted as of now with six passengers.” The company has said the aircraft's propulsion remains electrically driven. However, Schmidt explained that the design leaves room for a turbo-generator that could potentially recharge the batteries during flight. “We have enough space allocation so that we can consider putting in a turbo generator to charge our batteries mid-flight. But the energy transition from the battery to the motors is always going to be purely electric,” he said. Sarla first unveiled the Shunya prototype at the Bharat Mobility Global Expo in New Delhi in January 2025. The aircraft was presented as a six-passenger eVTOL with a maximum payload of about 680 kg and a targeted top speed of up to 250 km/h. The company said it was designed primarily for short urban journeys of roughly 20–30 km, while reported specifications indicated a potential range of up to 160 km with available battery technology. Sarla's roadmap has also included infrastructure and manufacturing. In November 2025, the company signed an MoU with the Andhra Pradesh government for a 500-acre aerospace campus in Anantapur, with an initial investment of ₹1,300 crore. Sarla described the project as an integrated Urban Air Mobility facility for eVTOL manufacturing and related activities. The company has said the facility is intended to support future aircraft production and air-taxi operations. The company's airport strategy also began taking shape earlier. Sarla Aviation and Bengaluru International Airport Limited signed a partnership agreement in January 2024 to explore an eVTOL ecosystem at Bengaluru airport, including connectivity between the airport and urban areas, vertiport infrastructure and an advanced traffic-management system for future eVTOL operations. Healthcare is another potential application. Bengaluru airport had an agreement with Sarla Aviation for last-mile connectivity and that Manipal Hospitals had also entered an agreement with the company for potential air-ambulance operations. More recent industry reporting indicates that hospitals and air-ambulance operators are increasingly exploring eVTOL partnerships as India develops its advanced-air-mobility ecosystem. The possible uses therefore extend beyond passenger air taxis. The technology could support airport-to-city transfers, last-mile connectivity, air ambulance operations, medical evacuation and cargo transportation. For India, airport connectivity is expected to be one of the earliest practical applications because road journeys between major airports and city centres can take considerable time. Naidu has said an airport-to-city journey that currently takes as long as two hours could potentially be reduced to around 20–30 minutes using eVTOL aircraft. The initial model is therefore expected to focus on short-distance and airport-linked journeys rather than replacing conventional public transportation. The Indian eVTOL market is not limited to Sarla Aviation. Chennai-based The ePlane Company is developing its e200X electric aircraft, while Hyderabad-based BluJ Aerospace is working on eVTOL technology for cargo and other applications. India is therefore developing multiple domestic approaches to advanced air mobility rather than relying solely on one manufacturer. There is also an international dimension to India's air-taxi plans. In 2023, InterGlobe Enterprises, the parent company of IndiGo, announced a partnership with US-based Archer Aviation to explore an all-electric air-taxi service in India, with an original 2026 target. However, that timeline has not materialised as initially envisaged. In 2026, IndiGo Ventures separately invested about ₹10 crore in Sarla Aviation, giving the Indian startup additional strategic backing. Importantly, the IndiGo investment should not be presented as confirmation that IndiGo itself will operate Sarla's eVTOL air-taxi service. Recent reporting said Sarla Aviation clarified that IndiGo's investment did not mean the airline was directly involved in its eVTOL operating plans. The regulatory process remains one of the biggest hurdles. Before commercial passenger operations can begin, eVTOL aircraft must demonstrate compliance with safety and airworthiness requirements and obtain the necessary certification. The DGCA will have to address aircraft design, flight operations, pilot qualifications, infrastructure, vertiports and integration with existing air-traffic systems. Infrastructure is another challenge. Commercial operations will require suitable landing and take-off locations, charging or energy infrastructure, maintenance facilities and systems for managing eVTOL traffic around densely populated areas. Battery performance, aircraft range, weather, operating economics and air-traffic management will also influence whether the 2028 target can be achieved at scale. Sarla's progress in 2026 nevertheless represents a significant shift from the concept and prototype phase. With the Sylla demonstrator having completed an extensive flight-test campaign and the company now holding DGCA Design Organisation Approval, its Shunya programme has entered a more advanced development and certification phase. The government's 2028 target will now depend on the pace of testing, transition-flight development, type certification, infrastructure creation and operational approvals over the next two years.

India Targets Electric Air Taxis By 2028 As Sarla Advances eVTOL Testing In Bengaluru

August 16, 2026

Fochville, South Africa: The preliminary accident report, released on 28 July 2026 by the Accident and Incident Investigations Division (AIID) of the South African Civil Aviation Authority (SACAA), found that the engine of a Bird Aviation Piper PA-28-180 registered ZS-ESZ was not producing power when the aircraft struck the ground near Fochville, Gauteng, on 27 June 2026. The report remains preliminary, with the investigation still ongoing and the AIID cautioning that its findings do not apportion blame or liability. According to the report, the operator was Bird Aviation, while the aircraft was being used under a hire-and-fly arrangement for hour-building. The operation was classified as Training under Part 91, and the aircraft belonged to the approved training organisation (ATO) from which it was hired. The accident involved two people, a 21-year-old Indian pilot and one passenger. Both were fatally injured and the aircraft was destroyed. The pilot held a valid Private Pilot Licence (PPL) and was building flight hours toward a Commercial Pilot Licence (CPL) through the ATO. The flight took place on the afternoon of 27 June 2026, when the pilot and passenger departed Lanseria International Airport (FALA) in Gauteng on an hour-building flight, intending to return to the same airport. The flight was conducted under visual meteorological conditions (VMC) and in accordance with Part 91 of the Civil Aviation Regulations. The flight had initially been planned for 0900Z, but departure was delayed because of persistent haze and low visibility. After conditions improved, the aircraft departed Runway 07 at 1325Z, as confirmed by an air traffic control officer at Lanseria. It then flew toward the Johannesburg General Flying Area (GFA), Flight Area Dangerous 182 (FAD 182). Multiple eyewitnesses later reported seeing the aircraft flying unusually low and performing unfamiliar manoeuvres. The aircraft subsequently flipped and began spinning to the left before impacting the ground. The crash occurred on a farm at Elandsfontein, south-east of Fochville, Gauteng, at coordinates 26° 35' 27.30" South, 27° 33' 41.24" East, with a field elevation of 5,124 feet. The accident was recorded at 1415Z. The pilot was a 21-year-old Indian national with a valid PPL. His licence was initially issued by the regulator on 25 May 2026 and was valid until 30 April 2027. His Class 2 aviation medical certificate was issued on 26 March 2025 and was valid until 31 March 2030. The report states that the aircraft type was endorsed on his licence and that he had no previous accidents recorded in relation to the investigation. The pilot had accumulated 132.2 total flight hours, including 19.4 hours in the previous seven days and 55.1 hours in the previous 90 days. He had flown 43.8 hours on the aircraft during the previous 90 days and had accumulated 122.7 hours on the Piper PA-28-180. The aircraft was a 1977-built Piper PA-28-180, a four-seat, single-engine, all-metal, low-wing aircraft with fixed tricycle landing gear. It was powered by a four-cylinder, naturally aspirated 180-horsepower Lycoming O-360-series engine. Its serial number was 28-3303, and it had accumulated 3,242.6 airframe hours by the time of the accident. The AIID found that the aircraft had valid registration and airworthiness documentation. Its current Certificate of Registration had been issued on 19 September 2025, while its latest Certificate of Airworthiness was valid until 31 October 2026. The aircraft underwent its mandatory periodic inspection on 13 March 2026 at 3,218.4 airframe hours, after which a Certificate of Release to Service was issued, valid until 12 March 2027 or 3,318.4 total airframe hours, whichever came first. The aircraft was maintained by an approved aircraft maintenance organisation whose certificate was valid until 30 June 2026. The organisation held Category A and Category C ratings for the aircraft's airframe and engine. The ATO's certificate had been renewed on 17 November 2025 and was valid until 28 February 2029. Fuel records showed that 111 litres of Avgas 100LL had been uplifted after the aircraft's flight on 26 June 2026, with the pilot refuelling the tanks before parking the aircraft. The Piper PA-28-180 has a fuel capacity of 189 litres, providing approximately six hours of endurance. The preliminary findings state that the aircraft departed Lanseria with full fuel tanks and no technical issues. However, fuel was found leaking from the aircraft after the accident. The report does not currently identify the fuel leak as the cause of the engine power loss. Weather conditions were favourable and were not considered a contributing factor. The 1400Z METAR from Lanseria recorded winds from 300° at 7 knots, CAVOK visibility, a temperature of 16°C, scattered clouds at 4,500 feet, a dew point of 5°C and QNH of 1026 hPa. The aircraft's navigation and communication equipment had no recorded defects before the flight. It was not equipped with a flight data recorder (FDR) or cockpit voice recorder (CVR), and the report states that neither was required for this aircraft type. The wreckage examination showed that the aircraft hit the ground in a steep nose-down attitude at high speed with little forward momentum. The debris was concentrated around the impact point, with a crater being the only ground scar identified. The aircraft came to rest facing south-east. Investigators found that the ailerons could not be moved and were both in the down position, while the elevator and rudder moved freely. The landing gear had broken and collapsed rearwards. Both wings suffered severe leading-edge damage and accordion-like deformation that ruptured the fuel tanks. The damage was consistent with heavy compressive loading during the steep, rapid-impact sequence. The top engine cowling had separated from the aircraft and was found approximately 10 metres ahead of the main wreckage. The engine cradle was deformed and the engine was facing slightly to the right. The propeller showed asymmetric damage, with one blade bent rearwards and the other showing little or no deformation. Neither blade displayed S-curve bending. The AIID said the damage pattern was consistent with the propeller being non-rotating at impact. This evidence, together with eyewitness accounts of the pilot apparently attempting to restart the engine, led investigators to conclude that the engine was not producing power at the time of impact. However, the preliminary report does not yet establish the underlying reason for the loss of engine power. The instrument panel was broken into multiple pieces, with several indicators dislodged from their original positions. The report does not provide a final interpretation of the instrument evidence at this stage. There was no evidence of a pre- or post-impact fire. Investigators considered the accident not survivable because of the extent of cockpit damage. Emergency responders reported that the pilot-in-command was not wearing his seat belt and was consequently thrown from the aircraft. Medical and pathological information is reserved for the final report. The aircraft was operating in the Johannesburg GFA within FAD 182, outside the Terminal Control Area. FAD 182 extends from the ground to Flight Level 100, or 10,000 feet, except where it intersects the TMA. Bird Aviation also used the Safely Track Me application to monitor flights. The system relied on the pilot's mobile-phone GPS signal. Tracking was active when ZS-ESZ departed Lanseria, but shortly after the aircraft exited the Johannesburg Special Rules Area West TMA, the phone stopped transmitting its GPS position and the aircraft could no longer be tracked through the application. The AIID's preliminary findings confirm that the pilot was qualified and medically fit for the flight, the aircraft was being used under a valid hire-and-fly arrangement for hour-building, the operator/ATO held a valid certificate, the aircraft had valid registration and airworthiness documentation, and its maintenance records were up to date. The investigation therefore establishes several key facts but has not yet determined the precise cause of the accident. The aircraft left Lanseria with full fuel and no known technical issues; the engine was not producing power at impact; weather was not a factor; and the aircraft entered a steep, high-speed descent before striking the ground. The AIID is continuing to examine other aspects of the accident that could have safety implications. No safety recommendations have been issued at this stage. The AIID said these will be addressed in the final report. The investigation was classified as a Category 1 accident. The AIID appointed an investigator-in-charge and a co-investigator, dispatched investigators to the site and notified the relevant states and organisations under South African regulations and ICAO Annex 13. The AIID will lead the investigation and issue the final report. The AIID has warned that the preliminary report is based on evidence gathered during an ongoing investigation and that information may change if additional evidence emerges. Accordingly, the current finding should be described as the engine not producing power at impact, rather than stating that investigators have already determined the cause of the engine power loss.

SACAA Preliminary Findings Show No Engine Power At Impact In Fatal South Africa Crash

August 15, 2026

Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 6

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 6

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - Part 5

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 5

From Demonstrations to Networks: The Real Test of Advanced Air Mobility - PART 4

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 4

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Citywide Networks Must Be Designed Around Real Travel Patterns

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 3

From Demonstrations to Networks: The Real Test of Advanced Air Mobility Part 2- Aviation Today Perspectives

From Demonstrations to Networks: The Real Test of Advanced Air Mobility – Part 2

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