Recurring concern
Ineffective controls preventing access to railway tracks
- Reports that mention this concern
- 24
- Times this concern has been raised
- 31
- Stated actions linked to this concern
- 60
What this concern includes
Includes failures of controls specifically dedicated to preventing or restricting access to railway tracks, including physical barriers or mitigation measures and responses to identified railway-access risks or recommended remedial actions.
What is not included
- Excludes generic failures in investigation, documentation, training, staffing or governance unless they are directly tied to a dedicated railway-track-access control.
- Excludes railway hazards unrelated to preventing access to the tracks.
- Excludes general infrastructure or highway safety deficiencies that do not concern access to railway tracks.
Trends
Reports over time
Reports mentioning this concern, over time
Reports about this concern issued each year.
* 2026 is projected from reports observed to 7 Sep 2026.
Most frequent recipients
Most frequent recipients
Reports about this concern sent to each recipient.
Reports and published responses 24 reports
See individual reports that have raised this concern, and the actions taken in response
-
Concerns raised1
Insufficient railway boundary fencing in areas used by dog walkers and others
Linked response
- Network Rail
Stated actions An action is something a respondent says it has done, is doing, or plans to do in response to the concern raised.3
-
Network Rail
Reassess the Icknield Way boundary risk using the fencing standard after the incident.
-
Network Rail
Carry out three-monthly inspections of the Icknield Way fencing to manage its increased risk rating.
-
Network Rail
Renew the Icknield Way fencing with a scheduled replacement in 2019/2020.
Respondent positions A position is what a respondent says about the concern when they do not describe a specific action.1
-
Network Rail
Existing compliant fencing, three-monthly inspections and scheduled renewal are considered sufficient pending replacement.
-
Concerns raised1
Failure to prevent public access to live rails at ground level
This report raised 1 other concern. They are not shown here because they do not form part of this recurring concern.
Linked response
- Network Rail
Stated actions An action is something a respondent says it has done, is doing, or plans to do in response to the concern raised.3
-
Network Rail
Continue developing reasonably practicable safety solutions for the ground-level conductor rail system.
-
Network Rail
Install platform-end gates and anti-trespass measures at more than 50 South East route stations, with works already completed at 30 locations.
-
Network Rail
Improve fencing at higher-risk locations through a programme including £800,000 of work due for completion by April 2019.
Respondent positions A position is what a respondent says about the concern when they do not describe a specific action.1
-
Network Rail
Converting or replacing the ground-level conductor rail is not reasonably practicable because of the railway system’s complexity and cost.
-
Concerns raised2
Easy public access to the railway track from the bridge
Lack of warnings about the dangers of accessing the railway track
Linked response
- Network Rail Infrastructure Limited
Stated actions An action is something a respondent says it has done, is doing, or plans to do in response to the concern raised.2
-
Network Rail Infrastructure Limited
Install wire mesh panels with base-plated fence posts on the parapet walls to deter access to the track.
-
Network Rail Infrastructure Limited
Erect a warning sign describing the dangers, Network Rail ownership and trespass prohibition.
-
Concerns raised2
Inadequate trespass deterrence and fencing around the foot crossing
Inadequate physical separation between foot crossing users and the railway
This report raised 2 other concerns. They are not shown here because they do not form part of this recurring concern.
Linked response
- Network Rail
Respondent positions A position is what a respondent says about the concern when they do not describe a specific action.2
-
Network Rail
Anti-trespass matting is not considered appropriate because there is no evidence of shortcuts or trespass at the crossing.
-
Network Rail
Further boundary mitigation is not required because fencing is in good condition, fit for purpose, compliant, and unrelated to the incident’s access route.
-
Concerns raised1
Inadequate fencing beside the railway track
Linked response
- Network Rail
Stated actions An action is something a respondent says it has done, is doing, or plans to do in response to the concern raised.2
-
Network Rail
Implement a mandatory fencing standard requiring risk-assessed boundary management measures for Network Rail-controlled infrastructure.
-
Network Rail
Complete enhancement work at identified Watford-area access locations, including installing additional palisade fencing around St Albans Road and Bedford Street.
Respondent positions A position is what a respondent says about the concern when they do not describe a specific action.1
-
Network Rail
The boundary fencing was compliant and inspections identified no faults requiring repair in the St Albans Road and Bedford Street area.
-
Concerns raised1
Unsafe track access from platforms
Linked response
- Network Rail
Stated actions An action is something a respondent says it has done, is doing, or plans to do in response to the concern raised.2
-
Network Rail
Install platform-end fencing and anti-trespass panels at both ends of platforms 2, 5 and 6 and the London end of platform 1.
-
Network Rail
Install equivalent platform-end fencing and anti-trespass panels at the country end of platform 1 by the end of July 2017.
-
Concerns raised1
Failure to maintain fencing and walls separating the public footpath from the railway line
Linked response
- Network Rail
Stated actions An action is something a respondent says it has done, is doing, or plans to do in response to the concern raised.5
-
Network Rail
Review active fencing upgrade proposals for both sides of the incident section.
-
Network Rail
Deliver planned fencing and boundary repairs in the incident section, restoring smaller stone-wall sections and replacing failed larger sections with lineside fencing.
-
Network Rail
Complete an extensive lineside fencing upgrade north of the location between Spittal and Berwick.
-
Network Rail
Conduct a site walk-through between Scremerston and Spittal to assess boundary robustness.
-
Network Rail
Plan further works to improve boundary robustness between Scremerston and Spittal.
-
Concerns raised1
Lack of an alarm or warning to the signaller when a person passes through the gate to the tracks at the end of the platform
No linked response statementsNo respondent-stated action or position is linked to these concerns in the published data.
-
Concerns raised1
Lack of a physical barrier at the end of platform three
This report raised 1 other concern. They are not shown here because they do not form part of this recurring concern.
Linked response
- Arriva Rail North Limited
Respondent positions A position is what a respondent says about the concern when they do not describe a specific action.1
-
Arriva Rail North Limited
Responsibility for barriers and fencing preventing track access lies with Network Rail as part of the station infrastructure.
-
Concerns raised1
Inadequate deterrence and hindrance provided by railway access gates and fencing
This report raised 1 other concern. They are not shown here because they do not form part of this recurring concern.
Linked response
- Network Rail Infrastructure Limited
Stated actions An action is something a respondent says it has done, is doing, or plans to do in response to the concern raised.1
-
Network Rail Infrastructure Limited
Deliver over 600 metres of fencing and upgrade nearby gates to deter unauthorised railway access.
Actions and positions describe what organisations say in published responses. Implementation is not independently verified.
Data last updated 7 September 2026