TL;DR On 2 November 2019, at Taipei Taoyuan Runway 05L hold short (taxiway S1), an unidentified man climbed into the main gear of China Airlines CI28. Asiana 712, holding behind, spotted him visually and alerted Taipei Tower. The takeoff was aborted. There is no TTSB report for this event — because it falls outside the safety-investigation mandate — and no standalone CAA aviation safety bulletin. The public record is press reporting from CNA / LTN, a follow-up piece four months later, and a tower-audio recording hungATC prepared from LiveATC reception and published on YouTube (288,369 views).
Some incidents never get a final report
How public record forms inside an official vacuum
Major safety events typically travel a well-defined public-record path: TTSB investigates, DFDR and CVR are impounded, a written report arrives 12–18 months later. Technical detail becomes public knowledge at that point.
CI28 did not.
- The aircraft never took off — no collision, no injury, no airframe damage.
- The classification is airside intrusion / security, handled by the Aviation Police, the Taoyuan District Prosecutors' Office, and the Taoyuan International Airport Corporation.
- The CAA issued statements through the press but not an Aviation Safety Bulletin.
Which leaves the public with:
- About ten news pieces (Chinese + English) from the day of the event and the days after;
- A tower-audio recording we prepared from LiveATC reception, captioned bilingually, and published on YouTube — 288,369 views as of this writing.
- An ETtoday follow-up from 3 March 2020 covering the intruder's eventual court appearance.
These three source types triangulate — quotes the press cited can be heard verbatim on the tape; the audio timeline matches the flight-delay window in the reporting. Here the four minutes of tower audio is not a supplement to a report; it is primary evidence, because there is no final report to supplement.
This is why the record deserves systematic archiving. A YouTube video can be taken down; the same material inside a coordinate-anchored, citation-traceable structure on a permanent URL can be searched, cited, and revisited long-term.
2 November 2019 · Taoyuan south runway
13:35 pushback · 14:08 halt · ~16:30 replacement airframe departs
Reconstructed from CNA and LTN:
13:35 CI28 (Boeing 737-800, B-18658) pushes back from a Terminal 1 gate, bound for Palau (ROR), 149 passengers.
13:55 The aircraft reaches the south runway (05L/23R) and holds short at taxiway S1. Asiana OZ712 rolls up behind shortly after, same hold.
~14:05 A man crosses the airside perimeter from the west, moves through the runway environment, reaches CI28's right side, and climbs into the main gear bay. Airport Corporation VP Dan Zhaobi stated to CNA that day this was the first such event in Taoyuan's history.
14:07–14:10 OZ712's crew spots him visually[16] and radios Taipei Tower in English. The detector is the crew of the aircraft behind — not tower radar, not airfield security.
"Tower, Asiana 712 — somebody on the tire system."
14:10 Tower instructs CI28 hold present position. Takeoff halted. The captain comes back on the channel with his own question — should he shut down an engine? The controller coordinates with airport operations, then confirms: shut down the right engine.
"Tower, Dynasty 028 — should I shut down one engine?"
~14:25 Aviation Police and airport operations vehicles approach from the west side of the aircraft.
~16:30 The intruder is detained. CI28 returns to the gate. A replacement 737-800 (B-18650) redeparts the CI28 flight[15] at approximately 16:30. Simple Flying reports 16:20[20]; CNA reports 16:40. Roughly three hours' delay.
On the intruder: initial reporting called him a "John Doe" — no match in Taiwan's entry/exit database, refused to speak, possessions included a Russian-language Orthodox Bible, a reflective vest, barbecue lighters, and a hand-drawn map. At his court appearance four months later he spoke Mandarin, acknowledged the trespass, and was convicted under the Immigration Act pending deportation. Final nationality was never disclosed in the public record we located — we do not fill in that gap.
How the recording reached the public
288K-view YouTube upload · press citations · five registers in four minutes
After the event, hungATC took LiveATC-received Taipei Tower audio (~118.7 MHz), assembled the CI28 / OZ712 segment with bilingual captions, and published it on YouTube. At the time of writing (2026-04-23), that upload holds 288,369 views — the most-trafficked first-hand audio record of this event in public circulation.
In the absence of a TTSB or ASC report and with the CAA communicating only through press statements, those 288K views plus the major-outlet citations form the primary public record of what happened on 2 November 2019.
Press outlets that cited the recording as reporting material: CNA, LTN (day of), LTN (prosecution), PTS, The News Lens, Simple Flying, ETtoday (four-month follow-up).
The tower channel is the player in the right column — it stays on screen as you read.
The recording shifts register five times in 3 minutes 50 seconds: Korean-accented English (OZ712), Taiwan-accented English (CI28), the controller's English to Asiana, the controller's Mandarin to China Airlines, and — inside the Mandarin stretch — the controller-to-airfield-operations coordination layer. Read as a transcript, those shifts flatten to a bilingual table. Listen, and they're audible. This is one reason we insist on archiving audio and transcript together, not either alone.
A few moments worth hearing:
00:27— Tower's first attempt to parse OZ712:"Confirm people on board, and say again after". You can hear a controller who doesn't yet trust what he's been told, asking for a procedural readback.01:37— CI28 comes up for the first time:"Affirm, we hold present position."Asiana had been relaying the holds up to this point; this is China Airlines directly acknowledging.03:08— The captain's own initiative:"Tower, Dynasty 028. Should I shut down one engine?"(translated from Mandarin). The shutdown request came from the pilot, not the tower. The controller checks with airport ops before responding. This is the "pilot intent takes precedence over ground coordination" norm actually running.
Triangulation when there is no final report
Three sources, mutual corroboration
Without an official report, validation relies on sources checking each other — quotes the press cited can be heard verbatim on the tape; audio timing matches the flight-delay window in the reporting. The table below triangulates observable facts across three source types:
| Observable fact | Press | Tower audio | YouTube captions | Result |
|---|---|---|---|---|
| Takeoff halted because aircraft behind saw intruder | CNA, LTN | OZ712: "somebody on the tire system" | Bilingual captions align | ✓ |
| Engine shutdown requested by pilot | LTN cites tower channel | 03:08 Mandarin: "我是不是要關一具發動機" | Captions align | ✓ |
| Right engine shut down | CNA: "shut down one engine" | 03:47 controller specifies right | Captions align | ✓ |
| Replacement airframe departure | CNA 16:40, Simple Flying 16:20 | Not in recording | — | Unresolved (±20 min) |
| Final nationality | Press speculation "Russian/Belarusian"; ETtoday follow-up does not name | — | — | Not verifiable |
Two things need to be clear:
- Tower audio does not reconstruct causation. It tells you "trailing aircraft called, leading aircraft stopped, right engine shut down." It does not tell you where the airside perimeter was breached, what path the intruder took, or why he was not seen earlier — those would require CCTV, airport security records, and a proper inquiry. None of that is in public circulation.
- The YouTube compilation's captions are second-order. Whoever produced it translated English lines to Chinese and Chinese lines to English for reach, and the captions are not a verbatim transcript. Our transcript is authored against the audio, not the captions.
Within the narrower band of what a tower channel can observe, the three source types corroborate each other and do not conflict. That is not a claim that causation is established. It is a claim that the tower-observable layer of this event has a public record.
Common questions
Boundaries and replicability
Why no TTSB report? TTSB's scope is major transportation accidents — collisions, crashes, serious damage, casualties. CI28 never took off and no one was hurt; it is classified as airside intrusion / security, outside TTSB's statutory jurisdiction. By design, not oversight.
Why no standalone CAA aviation safety bulletin? CAA ASBs typically address safety procedures, technical notices, or airworthiness directives. Airside intrusion, while safety-adjacent, sits in the airport-security perimeter handled by the airport company and Aviation Police; communicated through press rather than a formal ASB.
So what is hungATC's role here? We took LiveATC-received Taipei Tower audio, assembled the CI28 / OZ712 segment with bilingual captions, and published it on YouTube — that 288K-view video is ours. This case page takes the same material further: a permanent URL, a timestamped transcript, a map, a citation chain, JSON-LD metadata. YouTube handles reach; this page handles preservation.
Difference from LiveATC, FlightRadar24, FlightAware? LiveATC is the upstream — raw channel reception and best-effort archive. FR24 is ADS-B tracks. Both are category infrastructure. We do event-level curation on top — one slug per case, a complete source chain, a traceable evidence table. Complementary, not competitive.
Can anyone else do this? Technically, yes: the YouTube file is downloadable, LiveATC's original feed is public, press reports are public. The cost is editorial — slicing four minutes of audio into 44 timestamped clips, proofreading a bilingual transcript, verifying every news link, matching the map coordinates to the actual S1 geometry. An afternoon's work, not an algorithm.
The YouTube video already exists — why this page too? Because public record does not assemble itself. Without a TTSB report, press articles drift off front pages into page-three search results; a YouTube upload can disappear via algorithmic moderation, a copyright claim, or a policy change. Putting the same material behind a permanent URL, described by structured schema.org NewsArticle + AudioObject metadata, is the cheapest form of record preservation — if YouTube's copy vanishes, this one's still here.
Coda
While the event unfolded, a public tower frequency was being recorded by LiveATC. Years later, that recording is still replayable, still independently verifiable, still citable — not because of anything we did, but because the channel was public, and because someone kept the tape.
That is a property of the ATC-audio category: it belongs to no outlet, and not to us. It belongs to anyone who can legally receive that channel. The work on this page is simply to convert "in principle receivable" into "in practice indexed" — a four-minute audio file, a 44-line transcript, ten numbered event markers, a citation chain, all living at a permanent URL that isn't going to drop off a front page.
An uninvestigated event can still be fully recorded — if someone is listening at the moment, and someone else makes it searchable afterward.
Related work
- LiveATC.net Global ATC channel archive since 2004. Source of the tower audio on this case.
- Bellingcat OSINT investigative journalism. Their editorial standards are the reference for how this piece is structured.
Primary sources
- CNA Day-of Chinese reporting (taxiway S1, south runway, 149 pax, replacement at 16:40)
- Liberty Times Names OZ712's captain as the visual alert source
- ETtoday 2020-03-03 follow-up (court appearance, conviction, deportation pending)
- Simple Flying First full English report (names OZ712, B-18658, Palau)
- hungATC on YouTube Tower audio (LiveATC-sourced) + bilingual captions, 288K views
Sources last updated: 2026-04-23 · If you spot a factual error or a broken link, please email hi@chien.digital.
Note The audio was received on LiveATC's public Taipei Tower feed and prepared, captioned, and published on YouTube by hungATC. This page's transcript, timeline, map coordinates, and citation list are freely usable for media verification, academic research, or teaching purposes. Questions or collaboration inquiries: hi@chien.digital.