Pilot Deviation Causes Damage to Runway Edge Lights in Chennai

DGCA investigation highlights pilot error leading to damage of runway edge lights during takeoff at Chennai International Airport.
GopiGopi
4 mins read
Taxiway K, illustrating the lead line the pilot deviated from during take-off
Not Started

1. Incident Context and Regulatory Oversight

The Directorate General of Civil Aviation (DGCA), India’s civil aviation safety regulator, investigated a February 2025 runway incident at Chennai International Airport involving a Star Air flight bound for Bengaluru. The event did not result in casualties or aircraft damage but led to infrastructure damage on an active runway.

The incident occurred during the take-off phase, a critical segment of flight operations where strict adherence to ground markings and standard operating procedures is essential. Such incidents, even without human injury, carry systemic safety implications for airport operations and regulatory credibility.

DGCA’s role in conducting a final investigation and issuing safety recommendations reflects its statutory mandate to ensure compliance, prevent recurrence, and maintain international aviation safety standards under ICAO norms.

Failure to rigorously investigate and document such incidents can normalise procedural deviations, weakening institutional safety culture and increasing latent risks in high-density airports.

Aviation safety is built on zero-tolerance for deviations during critical phases. Ignoring minor infrastructure damage risks eroding procedural discipline, which can later manifest as major safety failures.


2. Nature of Deviation and Immediate Findings

The DGCA concluded that the pilot in command deviated from the lead line on Taxiway K, aligned the aircraft on the edge line of Runway 07, and initiated the take-off roll. This resulted in damage to seven runway edge lights on the right side of the runway.

Between 4.53 p.m. and 7.41 p.m., there were 45 aircraft movements at the airport, none of which reported airfield abnormalities. The damage was discovered later during a routine runway inspection, highlighting the challenge of detecting ground-level deviations in real time.

The aircraft itself operated six sectors after the incident and underwent a layover inspection at Bengaluru, where no abnormalities were found in the landing gear. This underscores that infrastructure damage may not always be accompanied by immediate aircraft indicators.

If such deviations remain undetected or under-reported, they may compromise runway integrity and night or low-visibility operations, affecting overall airport safety.

The incident demonstrates that procedural non-compliance can exist without immediate technical alerts. If monitoring and reporting systems do not capture such deviations promptly, regulatory feedback loops weaken.


3. Safety Implications for Airport and Flight Operations

Runway edge lights are essential visual aids, particularly during night operations and adverse weather, guiding pilots on runway alignment and boundaries. Damage to these lights directly affects runway serviceability and operational safety margins.

The fact that seven lights were damaged without immediate detection reveals gaps in situational awareness, coordination between pilots and air traffic services, and post-departure reporting mechanisms.

High aircraft movement density, as seen with 45 movements in under three hours, amplifies the systemic risk. Even isolated deviations can have cascading effects in congested airspace and busy airports.

If repeated, such incidents can undermine international confidence in airport safety management systems, with implications for audits, airline operations, and insurance liabilities.

Infrastructure safety is cumulative. Ignoring minor damage today raises the probability of operational hazards tomorrow, particularly in high-traffic aviation ecosystems.


4. Regulatory Response and Capacity-Building Measures

Based on the probable cause, the DGCA issued safety recommendations focusing on crew training and airport familiarisation. The regulator directed the airline operator to impart training aligned with its Flight Crew Training Manual.

Airport familiarisation training before assigning pilots to new airports was emphasised as a procedural safeguard. This reflects recognition that local airport layouts, taxiway geometry, and visual cues vary significantly and require structured orientation.

The response prioritises preventive capacity-building over punitive action, aligning with modern safety management systems that focus on human factors and systemic correction.

Without consistent training reinforcement, procedural deviations may recur across operators, indicating a broader institutional rather than individual lapse.

Regulatory effectiveness lies in learning-based correction. If training gaps are not addressed, compliance becomes nominal, and safety oversight shifts from preventive to reactive.


Conclusion

The Chennai runway edge light incident highlights how minor procedural deviations can expose systemic vulnerabilities in aviation safety governance. DGCA’s investigation and training-focused recommendations reinforce the need for continuous capacity-building, robust monitoring, and strict adherence to ground operation protocols to ensure long-term safety and institutional resilience in India’s rapidly expanding civil aviation sector.

Quick Q&A

Everything you need to know

Incident overview: The Directorate General of Civil Aviation (DGCA) concluded that the damage to seven runway edge lights on Runway 07 was caused by the pilot in command of Star Air flight SDG 8216. While taxiing from TWY K, the pilot deviated from the designated lead line and aligned the aircraft along the extreme right side of the runway edge line before initiating the takeoff roll.

Impact: The deviation resulted in seven runway edge lights being physically damaged. Fortunately, all 34 passengers and six crew members on board were unharmed, and there was no fire incident. The aircraft completed its planned six sectors of the day before post-flight inspection at Bengaluru confirmed no abnormalities in the landing gear.

Significance: This incident highlights the importance of strict adherence to taxiway guidance lines and runway alignment protocols. Even minor deviations during taxi or takeoff can cause damage to airport infrastructure, which may impact operational efficiency, safety, and airport maintenance costs.

Understanding airport layout: Airport familiarisation training equips pilots with comprehensive knowledge of taxiways, runways, apron areas, and airport lighting systems. For instance, the DGCA investigation revealed that the Star Air pilot deviated from the lead line on TWY K, emphasizing the need for pilots to be familiar with precise taxi routes.

Risk mitigation: Such training ensures that pilots are aware of potential hazards, including runway edge lights, obstacles, and ground markings. Familiarity with the airport reduces the likelihood of misalignment or incorrect positioning during taxiing and takeoff, mitigating risks to both aircraft and airport infrastructure.

Regulatory compliance: As per DGCA safety recommendations, airlines must provide airport-specific training before assigning pilots to new airports. Proper familiarisation aligns with ICAO standards and national aviation safety regulations, ensuring safe and efficient ground operations.

Data collection and analysis: DGCA conducted a detailed investigation by examining the flight path, taxiway alignment, and runway positioning of Star Air flight SDG 8216. They reviewed the aircraft's movements between 4.53 p.m. and 7.41 p.m., including 45 other aircraft movements, to rule out other potential causes.

Aircraft inspection: Post-flight inspections at Bengaluru checked the main landing gear and nose landing gear, which revealed no abnormalities, confirming that the aircraft itself had not been damaged. DGCA coordinated with the airline to check for any hidden issues.

Conclusion and probable cause: The investigation concluded that the damage occurred due to the pilot deviating from the lead line on TWY K and aligning on the runway edge line, thereby initiating takeoff and hitting the edge lights. DGCA also issued safety recommendations, emphasizing crew training and airport familiarisation.

Deviation from lead line: The DGCA report indicates that the pilot deviated from the designated lead line on Taxiway K, which is critical for guiding aircraft safely to the runway centerline.

Lack of airport-specific familiarisation: The incident suggests that the pilot may not have been fully familiar with the specific taxiway and runway layout of Chennai Airport, underscoring the importance of airport familiarisation training before assignment.

Operational complacency: Routine flights often lead to reduced attention to ground markings. Despite this being a scheduled flight with experienced crew, minor lapses in alignment procedures can cause significant infrastructure damage. DGCA’s recommendation to provide targeted crew training is aimed at addressing such human-factor risks.

Training and familiarisation: DGCA recommended that airlines impart specific airport familiarisation training to pilots before assigning them to new airports. This addresses the root cause of runway incidents by ensuring pilots are aware of taxiway layouts, runway markings, and lighting systems.

Human factors focus: Beyond procedural compliance, safety recommendations focus on reducing human errors through repeated training and awareness. Since most runway incursions or damage events involve human error, such measures enhance situational awareness and decision-making.

Organisational and systemic impact: By mandating airline compliance with safety training manuals, DGCA strengthens institutional accountability. Proper implementation can prevent infrastructure damage, reduce operational disruptions, and ensure safe passenger operations. However, continuous monitoring and audits are necessary to ensure that these recommendations translate into actual safety outcomes at airports nationwide.

Chennai runway edge lights incident: The Star Air flight SDG 8216 is a clear example where a pilot’s misalignment on the runway edge line resulted in the damage of seven runway edge lights. While no injuries occurred, the incident had operational implications, including runway downtime for inspection and potential repair scheduling.

Operational and financial impact: Damaged runway lights require repair and testing, potentially delaying subsequent aircraft movements and increasing maintenance costs. Additionally, repeated incidents can undermine airport safety reputation and increase insurance and liability concerns.

Lesson learned: This case highlights that even minor deviations from taxiway or runway protocols can have cascading effects on airport efficiency, safety, and financial performance, emphasizing strict adherence to standard operating procedures and crew training.

Comprehensive training: Airlines should implement rigorous airport familiarisation programs for all pilots before assigning them to new or complex airports. This includes detailed briefings on taxiway layouts, runway edge lights, markings, and standard operating procedures.

Use of technology: Incorporating advanced taxi guidance systems, airport moving maps in cockpit displays, and enhanced situational awareness tools can help pilots maintain proper alignment, especially in busy or complex airports.

Monitoring and feedback: Post-flight reviews, simulator sessions, and continuous monitoring of deviations can identify trends and potential risks. Airlines should also foster a culture of safety reporting and proactive risk management, ensuring that human errors are identified and corrected before they lead to operational or infrastructural damage.

Attribution

Original content sources and authors

Sign in to track your reading progress

Comments (0)

Please sign in to comment

No comments yet. Be the first to comment!