Bus cancellations in Cork city have several recorded causes, and the reason attached to each cancelled trip decides what an authority can act on. In September 2026 the National Transport Authority (NTA) said driver unavailability was the most frequent reason for recent cancellations around Cork, and on 27 October 2026 the Irish Examiner reported that 6.3% of planned bus kilometres were not travelled in the first half of the year. An AVM that records every cancellation with a trip identifier, a time and a reason lets an operator and an authority discuss the same numbers.
What did the NTA say about Cork bus cancellations in September 2026?
On 6 September 2026, The Echo (Cork) published a statement from an NTA spokesperson under the headline "Cork buses are unreliable because of a lack of drivers, says transport authority". The NTA apologised to passengers for "ongoing unreliability" and said that the most frequent reason for bus cancellations in recent times around Cork had been related to "the unavailability of drivers", with fleet availability also having an effect.
The same report says the NTA meets Bus Éireann senior management weekly and that Bus Éireann has been hiring extra drivers for several months. The NTA also said that a new depot at Tivoli Docks should improve fleet availability. This article relies on The Echo's account of the statement.
What did Bus Éireann tell the Oireachtas about Cork drivers?
The driver position was already on the record a year earlier. TheJournal.ie reported on 1 October 2025 that Bus Éireann's chief executive, Stephen Kent, told the Oireachtas Transport Committee that Cork was the company's most immediate short-term recruitment challenge. According to that report, Cork was short of 17 drivers, with some in training, and Bus Éireann planned to go overseas that autumn to recruit drivers holding D licences.
These are two statements from two different dates. Neither gives the number of drivers short in September 2026, and this article does not estimate one.
How much service did Cork city buses lose in the first half of 2026?
The Irish Examiner article of 27 October 2026 states: "Overall, 6.3% of planned bus kilometres were not travelled in the first half of this year." The data run to mid-June 2026 and cover 13 four-week periods. The article describes lost kilometres as a metric used across Ireland that compares how many buses operate with the schedule.
Other figures in the article:
- The rate was 5.6% at the same point in 2025, and 8.5% in the second half of 2025.
- It rose from 5.4% in the first four weeks of 2026 to 7.6% in the period from mid-May to mid-June.
- More than half of these cases were the fault of mechanical issues, according to the article. Staffing was the next most common reason, followed closely by traffic.
The article also lists route-level results, expressed as a share of scheduled trips not operating rather than kilometres:
| Route | Share of scheduled trips not operating |
|---|---|
| 208 (Lotabeg to Curraheen) | 13% |
| 202 (Hollyhill to Mahon Point) | 9% |
| 207 (Donnybrook to Glenheights) | 7.5% |
| 203 (Lehenaghmore to Parklands) | 7.5% |
| 226 (airport) | 1% |
| 225 (airport) | 2% |
Two details deserve care. The headline figure is in kilometres and the route figures are in trips, so they cannot be mixed in one calculation. And the cause ranking in this article (mechanical first, staffing second) sits alongside the NTA's September statement that driver unavailability was the most frequent cause of cancellations. Different periods, different measures and different wording explain why both can be reported, and neither source allows one to overrule the other.
For how the NTA defines lost kilometres and applies deductions in its published contract report, see our article Bus Contract Penalties in Ireland: What the NTA Measures.
Why does the recorded reason for a cancellation matter?
On 20 March 2025, The Echo reported NTA records obtained through a Freedom of Information request by the Sinn Féin TD Thomas Gould. They covered 778 cancelled Cork city bus trips between 24 and 28 October 2024. The reasons recorded were:
| Reason recorded | Trips |
|---|---|
| Abnormal traffic congestion | 543 |
| Blocked road or roadworks | 101 |
| Staff absence, lateness or sickness | 96 |
| Bus breakdown | 14 |
| Shortage of drivers | 11 |
| Accident or medical emergency on the bus | 5 |
| Service interruption or exclusion request | 5 |
| No serviceable bus | 3 |
The eight lines add up to the 778 trips (we checked the total). According to the report, the NTA supplied only those five days and said it "does not hold records of this nature" for the rest of the period requested, which the request set at six months back from mid-February.
Three lessons follow for any operator, whatever the market:
- Categories overlap. "Staff absence, lateness or sickness" and "shortage of drivers" both describe a bus without a driver. Two controllers under pressure at 06:00 will not always choose the same label.
- Records cannot be rebuilt afterwards. A reason typed at the moment of the event costs seconds. In this case the NTA said it did not hold such records for the rest of the period requested.
- Periods and sources do not combine. A five-day sample, a September 2026 statement and a half-year kilometre rate measure different things. Each is useful alone and misleading when added to the others.
What happens to passengers when a cancellation is not reported?
The Echo's report of 6 September 2026 also covers real-time information. The NTA said bus operators are responsible for sending real-time information, including cancellation notifications, to the NTA, and that it is stressing this to operators. When a cancellation is not reported, the scheduled time of the bus continues to appear on real-time information, because without live data the app cannot tell a bus that is running from one that has been cancelled.
For a passenger this means a bus shown as due that will not arrive. GTFS Realtime, the open format widely used for such feeds, can mark a trip as cancelled, but only if the producer sends that information. The chain therefore runs from the controller or driver who learns of the cancellation, to the operator's system, to the feed, to the passenger's screen. Every manual step in that chain is a place where the information can stop.
How can an AVM help an operator record and publish cancellations?
The Pysae platform page lists, for Operations, "Alerts and incidents: service breaks, critical delays, immediate escalation", a live map with delays, advances and regularity per line calculated automatically, and "Automatic GTFS-RT, SIRI, ITxPT exports to regional calculators and AOM". The Operations module page covers the product.
For driver absences, the platform page lists, for Shift, "Real-time drag-and-drop dispatch: replace an absent driver in under 30 seconds" and a cyclic roster with automatic spread rules and labour regulation constraints. A fast replacement avoids a cancellation when a spare driver exists. When none exists, the trip is cancelled, and the quality of the record then matters more than the speed of the dispatch screen.
A feed can only publish what the system has recorded. The practical question to ask of any AVM, including ours, is therefore: when a controller marks a trip as cancelled, where does that event go, and how does an operator check that the feed shows it?
Our earlier article on how scheduling software helps bus operators manage the driver shortage covers the planning side of the same problem.
What should a cancellation record contain?
The following fields are our suggestion for a record that serves both the authority and the operator. They are not an NTA requirement:
- The timetable trip identifier, line and direction.
- The scheduled start time of the trip.
- The time at which the cancellation was recorded, so that it can be compared with the scheduled departure.
- A reason from a short fixed list agreed with the authority.
- Whether the whole trip or only part of it was cancelled.
- The replacement trip or vehicle, if any.
On the reason list, separate the cases that call for different action: no driver assigned when the duty was planned, a driver absent on the day, a driver late, a vehicle unavailable, and a road or traffic cause outside the operator's control. A planning gap is fixed in the roster. A sickness absence is fixed in dispatch. Mixing them under one label hides which fix is needed.
One indicator is worth tracking from the first day: the share of cancellations that appeared in the live feed before the scheduled departure time. It measures the passenger-facing cost of an unreported cancellation directly.
What does the Cork case mean for operators elsewhere?
The Cork figures are specific to Cork city and to the sources cited here. They are not a measure of Irish bus services as a whole. What travels to other networks, in Ireland and in other English-speaking markets, is the structure of the problem: cancellations have several causes, the label attached to each one shapes the discussion with the authority, and an unreported cancellation stays visible to passengers as a scheduled bus.
Frequently asked questions
What is the main reason for bus cancellations in Cork?
According to The Echo's report of 6 September 2026, the NTA said the most frequent reason for recent cancellations around Cork had been the unavailability of drivers, with fleet availability also a factor. The Irish Examiner's half-year lost-kilometre figures, reported on 27 October 2026, rank mechanical issues first. The two use different measures and periods.
What is a lost kilometre?
The Irish Examiner describes lost kilometres as a metric used across Ireland that compares how many buses operate with the schedule. The article gives 6.3% of planned kilometres not travelled in the first half of 2026 for Cork city. The NTA's own definitions are discussed in our article on bus contract penalties in Ireland.
Does a cancelled bus always disappear from real-time apps?
According to the NTA, as reported by The Echo, it does not: when operators do not send the cancellation notification, the scheduled time of the bus continues to appear on real-time information.
Which Pysae modules relate to cancellations and absences?
The platform page lists alerts and incidents and GTFS-RT, SIRI and ITxPT exports under Operations, and real-time dispatch to replace an absent driver under Shift. How a cancellation is recorded and published on a given network is a configuration question best discussed in a demo.
Do these figures describe all Irish bus networks?
No. They concern Cork city and come from the press reports cited above. Other networks have their own data.
To see how Operations and Shift record absences and incidents on a network like yours, use the "Request a demo" button on this page.