From the Transportation edition of November 9, 2026
Singapore's LTA pauses ComfortDelGro AV U-turn tests in Punggol after a second Nov. 5 near miss
Land Transport Authority of Singapore; ComfortDelGro (Zig); Grab · Roadway safety; autonomous on-demand transit testing · Singapore
- Publisher
- The Straits Times
- Original publication
- Nov 8, 2026, 8:15 PM (updated Nov 9, 2026)
- Source retrieved
- 2026-11-10
- Event date
- 2026-11-05
What happened
Singapore's Land Transport Authority directed ComfortDelGro to pause autonomous-vehicle U-turns at a Punggol junction after dashcam video showed a CDG AV turning into the path of an oncoming vehicle on Nov. 5; LTA is investigating. The AV was testing a route for an enhanced on-demand service, not CDG's existing shuttle route. The same day, a Grab AV nearly hit a girl in Punggol, and Grab was directed to pause testing at certain junctions. No injuries are reported. The incidents surfaced through public dashcam videos, not operator reporting.
Why it matters
Shows a transport regulator using narrow, junction-level pauses as a precautionary control during AV service expansion. U.S. state DOTs and cities permitting AV or automated shuttle pilots can compare incident detection, reporting and pause authority. Singapore's single national regulator differs from U.S. federal-state-local splits.
Evidence and measured results
News report quoting LTA and the operator; no investigation findings, disengagement data or incident rates are published. The causal account is not yet established.
Limitations and uncertainty
Investigation ongoing; facts may change. Dashcam footage and captions come from a public Facebook group. Non-U.S. regulatory context. Vehicle technology partner (Pony.ai for CDG) is named in reporting only.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-09; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies permitting AV pilots lack tested processes for incident reporting, scoped pauses and public transparency.
- Stakeholders
- State DOT or city transportation director
- AV program manager
- Traffic safety engineer
- Public information officer
- Discovery questions
- What incident data must operators report, and how fast?
- Who can pause a maneuver or location, and on what criteria?
- How are public reports of near misses captured?
- Value hypothesis
- Clear pause and reporting rules can help agencies act quickly and transparently during AV pilots; no safety improvement is evidenced.
- Potential engagement
- Pilot-governance review of an AV or automated shuttle permit covering reporting, pause authority and resumption criteria.
- Unsupported claims
- Fault or cause of either near miss
- AV safety rates in Punggol
- That scoped pauses prevent future incidents
Pre-sales engineering
Role takeaway
- Fit
- Relevant to agencies overseeing AV testing on public roads or automated transit shuttles.
- Architecture and integration
- Operator event logs, onboard and roadside video, and agency incident systems need defined interfaces and retention.
- Prerequisites
- Defined operational design domain per route
- Operator data-sharing terms
- Incident classification scheme
- Constraints
- Different U.S. federal, state and local authority
- Operator proprietary data
- Ongoing investigation details unavailable
- Security
- Protect shared video and telemetry with access controls and retention limits.
- Proof of value
- Simulated incident drill measuring data delivery time
- Review of maneuver-level risk on new routes
- Audit of public-report intake
Delivery
Role takeaway
- Work
- Design and rehearse the AV incident, pause and resumption process for a pilot permit.
- Dependencies
- Permit conditions
- Operator cooperation
- Legal review of pause authority
- Ownership
- Transportation agency AV program manager with traffic safety lead.
- Skills and adoption
- Train staff to triage AV incidents and review operator telemetry.
- Governance checkpoints
- Permit includes reporting timelines
- Pause decision documented
- Resumption approved after review
- Acceptance criteria
- Operators report incidents within an agreed window
- Every pause has a documented resumption decision
- Public reports logged and answered
- Risks
- Public learns of incidents before the agency
- Pause criteria too vague to act on
- Data access disputes with operators
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Testing on new routes for on-demand service introduces maneuvers (U-turns, discretionary turns) outside the established shuttle route, which is where the near misses occurred.
Governance
Who approves, reviews and stays accountable for outcomes?
Regulator exercised scoped pause authority per junction and maneuver pending review; detection came from public video, raising questions about mandatory operator incident reporting.
Security and privacy
What data, permissions and controls need testing?
No cybersecurity or privacy issues are reported; the safety concern is vehicle behavior at junctions.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
No workforce detail; operators say they are reviewing with technology partners.
Procurement
What should contracts, pricing and exit terms secure?
Suggests pilot agreements should include regulator pause rights by location and maneuver.
Operating model
Which teams own the service once it runs?
The regulator, operator and technology partner share investigation; route expansion is staged on test routes before service.
Publication history
- 2026-11-09Transportation · Issue 127 resources
Stable resource ID: singapore-lta-pauses-cdg-av-u-turns-punggol-near-miss-2026-11-08