Flight SG-9046 | Registration: VT-SUO
Date: 30 March 2025 | Route: Jaipur (VIJP) – Chennai (VOMM), India
Introduction
On 30 March 2025, a SpiceJet de Havilland Dash 8-400 aircraft, registration VT-SUO, operating domestic flight SG-9046 from Jaipur to Chennai, experienced an in-flight alert after Jaipur ATC reported tyre debris found on the departure runway. The crew, unaware of any abnormalities at the time of take-off, chose to continue the scheduled flight. The aircraft landed safely in Chennai approximately two hours later without incident.
Post-landing inspection confirmed that tyre #2 – the left inboard main gear – had lost its tread during take-off. No additional structural damage or performance degradation was reported. SpiceJet confirmed that the aircraft had performed a normal landing and taxi to stand, with braking unaffected.
Flight Details
• Aircraft Type: De Havilland Canada Dash 8-400 (DHC-8-Q400)
• Operator: SpiceJet
• Registration: VT-SUO
• Engines: 2 × Pratt & Whitney PW150A
• Flight Number: SG-9046
• Departure Airport: Jaipur International Airport (VIJP), India
• Destination Airport: Chennai International Airport (VOMM), India
• Date of Incident: 30 March 2025
• Occupants: Unknown (typical Q400 capacity ~78)
• Phase of Flight: Enroute / Landing
• Runway Used (Departure): 26 (Jaipur)
• Runway Used (Arrival): 25 (Chennai)
• Weather Conditions: Not reported as a contributing factor
• Time of Notification: In-flight (by Jaipur ATC)
• Time of Landing: Approx. 2 hours after departure
Sequence of Events
Take-off from Jaipur
The aircraft departed from Jaipur’s runway 26 without any reported anomalies. Shortly after departure, Jaipur Air Traffic Control notified the flight crew that tyre debris had been located on the departure runway.
Enroute Flight
With no cockpit indications or abnormal flight characteristics, the crew assessed the situation and chose to continue towards Chennai. No flight diversions or emergency declarations were made.
Landing in Chennai
Upon arrival at Chennai, the aircraft executed a routine landing on runway 25. Braking performance was reportedly normal. The aircraft taxied to the assigned stand without any difficulty.
Post-Flight Inspection
After shutdown, ground engineers conducted a detailed examination of the aircraft’s landing gear. It was discovered that main wheel #2 (left inboard) had suffered a complete loss of tyre tread. However, the wheel itself remained structurally intact, and no damage to surrounding systems or structures was identified.
Technical & Operational Analysis
Tyre Failure Overview
Tyre tread separation typically occurs due to over-deflection, under-inflation, foreign object damage, or manufacturing anomalies. In this case, the tread likely separated during the take-off roll and detached completely once airborne.
Landing Gear Design
The Dash 8 Q400 is equipped with dual-wheel main landing gear assemblies. The loss of one tyre tread does not generally compromise the overall safety or integrity of the landing operation, particularly when the affected wheel remains pressurised and the failure is symmetric or isolated.
Cockpit Indications
There were no tyre pressure monitoring systems (TPMS) alerts or abnormal system messages during the climb or cruise phase. This aligns with the typical configuration of older Q400 variants which rely on visual post-flight inspections for certain mechanical anomalies.
Safety Actions & Airline Response
• Maintenance Action: The affected wheel assembly was scheduled for replacement. Full inspection of the gear structure and brake components was performed as a precautionary measure.
• Passenger Impact: There were no injuries or operational disruptions reported.
• Flight Continuity: The aircraft remained in Chennai for corrective maintenance and was expected to return to service after standard safety checks.
• Regulatory Notification: No emergency was declared, and the airline is not known to have initiated a formal investigation beyond standard post-incident protocols.
Conclusion
This tyre tread loss incident highlights the robustness of modern regional turboprop aircraft systems. Despite a partial failure of a main wheel component, the flight was completed safely with no adverse effects on performance or passenger safety. The crew acted appropriately given the information available in-flight, and the post-flight technical response ensured continued airworthiness.
While such incidents are rare, they reaffirm the importance of routine runway inspections and timely ATC coordination, both of which played a critical role in identifying the anomaly during this flight.
Disclaimer
This report is based on publicly available information and statements as of 2 April 2025. While every effort has been made to ensure accuracy, the final outcome of any internal or regulatory investigation may provide additional details. If you are the rightful owner of any referenced content and wish it to be removed, please contact takedown@cockpitking.com.
