2025-02 · NASA ASRS report 2212368
A320 Captain reported during landing at night on a snow covered runway the aircraft did not stop until entering the overrun.
ZZZ1 - ZZZ night landing in ZZZ during cold weather operations. I was reassigned to fly the ZZZ1 - ZZZ leg after my original flight to ZZZ2 was delayed several hours. I arrived at the aircraft approximately 37 minutes prior to push back and started downloading the paperwork. The First Officer (FO) had already loaded the FMC. Enroute; received report from Dispatch that ZZZ Runway Condition Code (RCC) was 5-5-3 for Runway 19. We confirmed by asking for airport conditions using ACARS. Based on our landing weight of 138.6 and and using the ZZZ 10-7D landing distance charts (no tailwind) we determined we needed a RCC of no less than 4 (this produced a landing distance around 5820 feet plus 220 feet for QNH correction; unless we burned fuel down to a landing weight less than 137.7 with no tailwind and QNH correction). Approximately 15 minutes later; Dispatch informed us that ZZZ had worked on runway and RCC was 5-5-4.We asked to be kept up to date on RCC if it changed and we would need to burn 900 lb of fuel if the RCC went back to 3. We also asked about using ZZZ3 (instead of ZZZ4) as an alternate if we needed to lower our landing weight more. In the end; we kept ZZZ4 as an alternate since we would be able to burn fuel down to an acceptable landing weight and still land in ZZZ4 with 4500 - 5000 lb of fuel with a BINGO of 8000 lb of fuel. We elected to descend early to burn more fuel and lower landing weight to around 138.3. We performed the ILS Z Runway XX. Broke out of overcast between ZZZZZ and ZZZZZ1 with moderate snow around 2500 feet AGL. FO asked for another braking action report and Tower said it was still 5-5-4. Autopilot and auto thrust off; on airspeed and glide slope with aircraft getting slightly high around 1100 feet; then back on glide slope by 900 feet. At 200 feet; I shifted the aim point to 500 feet from the approach end. At this point the FO asked Tower to lower the runway light intensity because it was hard to make out details on the snow covered runway with the bright lights. I noticed the runway's center 2000 feet was partially cleared of snow; but the approach and departure ends of the runway (~2000 feet on each end) were snow covered. Never noticed the light intensity decreasing. Landed approximately 1300 feet down runway (hard to tell exactly with snow covered runway) and close to VLS. Medium autobrakes were selected as per the 10-7 page; but I did not feel a deceleration or see the decel light illuminate so I immediately applied manual brakes to start the deceleration.Brakes seemed to work normally entering the center 2000 feet of the runway; but with 3000 feet remaining; the FO and I both noticed the brake's effectiveness was not what we needed to stop the aircraft on the runway. At this point we both applied full manually braking and the anti-skid was cycling. I said we are going into the overrun about 500 feet from end of runway. I continued using full reverse thrust and maximum manual braking. The aircraft entered the overrun around 15 - 20 knots until we stopped approximately 200 feet onto the paved overrun. At this point I moved the thrust levers to forward idle. We informed the Tower that we had stopped in the overrun and we were instructed to turn around and taxi to the gate. After informing Tower of the RCC being less than 4; we said the RCC was 1 or 2; the Tower noted we were fast on the runway (we were; due to the poor braking conditions). We performed a 360 degree turn in the overrun and taxied uneventfully to the gate. I performed walk-around after engine shutdown and no aircraft damage was observed.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.