What caused the rail delays between Mons, Brussels and Brussels Airport?
A damaged level crossing near Soignies delayed trains linking Mons with Brussels and Brussels Airport on Friday morning, 21 August, with some services losing substantially more time than SNCB’s initial estimate of five to 15 minutes.
The corridor is used for commuting into Brussels, regional travel within Hainaut and connections to Brussels Airport. Even a geographically limited infrastructure fault can disturb several linked services and create larger knock-on delays than the first network estimate suggests.
A damaged level crossing near disrupted trains from to and Brussels Airport on Friday morning, 21 August, delaying commuters travelling into the capital and passengers heading for flights. SNCB initially announced delays of five to 15 minutes, but , citing the Belga news agency and live passenger information, reported that several trains had accumulated substantially longer delays by about 10:00.
The immediate relevance for Belgium-based readers was unusually broad for a local infrastructure failure. The affected corridor carries workers and students from towards , while some services continue to . A fault outside could therefore upset office arrivals in the capital, onward domestic connections and time-sensitive journeys to the airport. The available reporting did not identify cancellations or confirm that passengers had missed flights, however.
SNCB described the incident in its passenger information as “damage” at a level crossing and said shortly before 10:00 that the duration remained “undetermined”, according to . That language conveyed the operational consequence but did not establish what damaged the installation, which crossing was involved or whether a technical failure, road vehicle or external event was responsible. No later restoration time was included in the archived report, so the disruption should not be presented as continuing beyond Friday without a fresh live-network check.
The geography matters. lies on railway line 96 between and , making it a pinch point for services connecting western with , and the capital. SNCB’s published route material shows that the corridor also supports trains running beyond central Brussels, including services associated with Brussels Airport. Here “Brussels” means the Belgian capital and its principal stations; Brussels Airport is in Zaventem, in , and is not inside the Brussels-Capital Region.
For passengers, SNCB’s perspective was practical: expected delay, affected route and an initially unknown end time. , the public company responsible for Belgium’s rail infrastructure, frames defective level crossings primarily as safety-critical infrastructure events. Its technical information explains that alerts from railway equipment are sent to the Rail Infrastructure Operations Center, where specialists can analyse the fault remotely and, where cameras are available, inspect the crossing before or alongside an intervention on site. These are complementary views rather than competing accounts: SNCB manages the journey and passenger information, while Infrabel manages the tracks, signalling and crossings.
The incident also illustrates why a small failure can spread through a busy railway timetable. A level crossing is part of the railway’s protective system, not simply a road barrier. If its safe operation cannot be established, railway traffic may need to be regulated while the equipment is checked, causing delays that propagate to following trains and later stops. ’s open-data portal lists public level crossings across its network and states that removing physical road-rail intersections is the most effective way to eliminate their inherent collision risk.
That longer-term policy provides the broader context, but Friday’s event remains a short, domestic mobility story rather than an international or EU-institutional one. It affected access to and Belgium’s main airport; it did not directly involve an EU body, and no response from the federal mobility authorities or local officials in was identified in the reviewed sources.
Travellers affected after the event can consult SNCB’s journey tools and request an official delay certificate. The unanswered questions are narrower but important: what caused the damage, how long repairs took and when normal traffic fully resumed. Unless SNCB or publishes a retrospective update, those points remain unconfirmed.
Impact
Regional — The disruption directly affected Walloon passengers travelling from Mons and through Soignies and Braine-le-Comte, then extended into the Brussels rail hub and towards Brussels Airport in Flanders.
Local — Passengers boarding in Mons, Soignies and Braine-le-Comte faced disruption on line 96 into Halle and the main Brussels stations. Because some affected services continued through the Brussels rail hub towards Brussels Airport-Zaventem, the consequences extended beyond the immediate level-crossing location into Brussels and Flemish Brabant. Travellers making station connections or heading to the airport were particularly exposed to delays exceeding SNCB’s initial estimate, although the available material does not quantify cancellations or missed connections.
What it means for you
For journeys on the Mons–Brussels–Brussels Airport axis, passengers should check SNCB’s live journey planner and ongoing-disturbances portal shortly before departure rather than rely on the initial five-to-15-minute estimate. Anyone connecting to an airport train should allow additional transfer time and verify the status of the specific service. Travellers affected on 21 August 2026 should retain their ticket and journey details if they intend to check eligibility under SNCB’s delay-compensation rules. The reviewed sources provide no confirmed restoration time or precise crossing location.
Opposing perspectives
- SNCB passenger-information perspective
SNCB framed the event through its immediate effect on journeys, announcing an expected delay range of five to 15 minutes and describing the disruption’s duration as “undetermined”. That concise operational framing helps passengers decide whether to travel but does not explain the technical cause.
- Infrabel infrastructure-safety perspective
Infrabel’s published material treats a defective level crossing as a safety-critical infrastructure alert requiring diagnosis and controlled intervention. Its broader position is that physically separating roads and railways is the most effective long-term way to eliminate level-crossing risk. This complements, rather than contradicts, SNCB’s passenger-facing account.
Who, where and what
Key people, places and terms in this story
Hainaut city and origin point on the affected rail axis.
Walloon province containing Mons, Soignies and Braine-le-Comte.
Major destination and rail hub affected by delays from the Mons corridor.
Belgian region containing the Hainaut section of the affected corridor.
Belgian region containing Brussels Airport and part of the affected services' onward route.
Show the full library (15)
Hainaut city and origin point on the affected rail axis.
Walloon province containing Mons, Soignies and Braine-le-Comte.
Major destination and rail hub affected by delays from the Mons corridor.
Belgian region containing the Hainaut section of the affected corridor.
Belgian region containing Brussels Airport and part of the affected services' onward route.
Hainaut town near the damaged level crossing that triggered the disruption.
Intermediate Hainaut town whose passengers were affected on line 96.
City on line 96 between Hainaut and the Brussels rail network.
Airport railway destination reached by some affected services.
Province containing Brussels Airport-Zaventem, where the disruption's effects extended.
Morning rail disruption caused by a damaged level crossing near Soignies.
Belgian passenger-rail operator that communicated disruption and estimated delays.
Belgian rail-infrastructure manager responsible for tracks, signalling and level crossings.
Brussels regional media outlet that reported longer delays at around 10:00.
Rail corridor connecting Mons and Hainaut communities with Halle and Brussels.
Sources & evidence
- View sourceBX1Primaryprimary· bx1.be· 21 August 2026Retrieved 26 August 2026· 42 days ago· Dated
- View sourceSNCB/NMBS line 96 route informationofficial· belgiantrain.beRetrieved 26 August 2026
- View sourceSNCB/NMBS passenger-information portalofficial· belgiantrain.beRetrieved 26 August 2026
- View sourceInfrabel technical-crossing monitoring briefingofficial· infrabel.be· 3 April 2019Retrieved 26 August 2026· 2739 days ago· Dated
Related topics
Related to this story
Pulse Insight — This topic connects to 10 associations and 3 funding programmes through the Wallonia ecosystem.
Live connections from the Belgium Impulse ecosystem — not recommendations.
This briefing was prepared with AI assistance and reviewed by a Belgium Impulse editor before publication. methodology.