Air Canada Rouge LP Flight ROU1717
Airbus A319 · Incident: landing area undershoot
From Toronto to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DCA25LA291
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Ongoing
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Airbus A319
- Aircraft type
- Airbus A319
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- C-GSJB
- Operator
- Air Canada Rouge LP
- Onboard fatalities
- Unknown
- Route
- From TorontoTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 129: Foreign
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Landing area undershoot
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None Possible conflict
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On August 14, 2025, about 1724 central daylight time (CDT), Air Canada Rouge flight ROU1717, an Airbus A319 airplane, registration C-GSJB, touched down short of runway 20L while landing at the Nashville International airport (BNA), Nashville, TN. There were no injuries to the ninety-three occupants onboard. A postincident inspection revealed that the airplane sustained minor damage. The regularly scheduled international passenger flight was operating under the provisions of Title 14 Code of Federal Regulations Part 129 from Lester B Pearson International airport (CYYZ), Toronto, Ontario, Canada to BNA. As part of the investigative process, the NTSB invited qualified parties to participate in the investigation, including the Federal Aviation Administration (FAA). In accordance with the provisions of Annex 13 to the Convention on International Civil Aviation, an Accredited Representative from the Transportation Safety Board of Canada (TSB), the State of Registry for the airplane, with Air Canada as their technical advisor. And an Accredited Representative from the Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA), the State of Design, with Airbus and European Union Aviation Safety Agency (EASA) as their technical advisors. The parties were organized into specialized investigative groups, each led by an NTSB group chair. These groups focused on the areas of Operations, Air Traffic Control (ATC), Meteorology, Cockpit Voice Recorder and Flight Data Recorder. HISTORY OF FLIGHT The flight crew consisted of a Line Indoctrination Training Captain, seated in the right seat, and serving as the pilot monitoring (PM), and a captain candidate, seated in the left seat, serving as the pilot flying (PF). The crew reported that ATC initially instructed them to expect a visual approach to runway 20L. However, due to rain over the airport, ATC later amended the clearance to the RNAV (GPS) Y 20L approach (see figure 1). The flight was cleared to the initial approach fix (IAF) WAYLN, then given radar vectors and subsequently cleared for the approach.
Figure 1. Instrument approach plate for RNAV (GPS) Y RWY 20L approach. The airplane was configured for landing at approximately 1,100 feet and met the operator’s stabilized approach criteria at both 1,000 and 500 feet; however, the stable call at 500 feet was missed by the PM. At the decision altitude (DA), the autopilot was disconnected. Around 200 feet above ground level (AGL), the crew encountered heavy rain, and the PF requested activation of the windshield wipers. Shortly after, the PF stated he had “lost the runway” but still believed the runway environment was visible. He asked whether a go-around should be initiated. The PM, who could see the runway environment—albeit distorted by rain—and believed the aircraft was on the glide path, responded that they were good to continue. At 20 to 30 feet radio altitude, the crew retarded the thrust levers to idle. About the same time, the PF was startled to see the runway threshold lights directly ahead of the aircraft’s nose. The crew perceived that the airplane touched down on the blast pad, a paved surface preceding the runway threshold. The remainder of the landing rollout and taxi were uneventful. Airport video surveillance captured the incident sequence and showed the airplane as it touched down short of the runway. Following the initial touchdown, the airplane rolled onto the pavement and impacted a runway threshold light. A post-incident inspection by airport personnel revealed that the left main landing gear contacted an airport service road approximately 420 feet short of the runway threshold. The right main landing gear touched down approximately 52 feet short of the paved surface, which was about 430 feet short of the runway threshold (see figure 2).
Figure 2. The left photo shows the left main tires witness marks on service road. The right photo shows the right main tires witness marks in grass short of paved surface. (Source: BNA airport.) A post flight inspection by maintenance personnel revealed mud on the airplane’s empennage and minor damage to one of the airplane’s tires.
Figure 3. Incident airplane's empennage. (Source: BNA airport.) The investigation continues.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record DCA25LA291
- Event ID
- 20250815200791
- Case number
- DCA25LA291
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, damage. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: e99601397382a18c23ce783f03a818b4b7889fd55b399e4b869daa5448558178; retrieved 2026-09-16T20:13:06.171Z.