IndiGo Flight 6E 225 Identified as VT-NOG After Srinagar Parking Incident
The aircraft involved in the September 4 taxiway collision at Srinagar airport has been identified as VT-NOG, with all passengers and crew safe.
2 reports on this incident · first at Sep 4, 2026, 4:13 a.m. ET
Earlier reports
Sep 4, 2026, 4:13 a.m. ETFirst report
IndiGo Flight 6E 225 Hits Guidance Pole While Parking in Srinagar; All Safe
An IndiGo flight, 6E 225, collided with a visual docking guidance system pole while parking at bay number 06 at Srinagar airport on September 4, 2026, according to prahaar.in. The incident occurred at approximately 9:02 AM after landing, while the aircraft was taxiing to the parking bay. All passengers and crew were evacuated using manual stairs, and the aircraft's nose section sustained minor damage. Airport operations continued normally after the incident.
The aircraft involved, registered VT-NOG, has not been further identified. The Directorate General of Civil Aviation is conducting a thorough investigation into the exact cause of the accident, which has not been determined. The investigation is ongoing.
Was this report accurate and useful?
Reference data
From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.
- Terrain elevation
- 5,210 ft
- Nearest aerodrome
- 6.6 miles NNE of Sheikh ul Alam International Airport (VISR/SXR)
Sources
Revision history
- Version 14 Sept 2026, 08:22current
First published.
- Version 14 Sept 2026, 08:13current
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.