Casualties unknown

Runway Incursion Involving a B737-300 at Singapore Changi Airport

SG

On November 28, 2020, an Airbus A320 was involved in an aviation accident near SG. Investigators recorded the probable cause as: The runway incursion occurred because the Pilot Flying assumed clearance to enter Runway 02C was granted, despite the instruction to hold short, and the Pilot Monitoring did not communicate the holding requirement due to being occupied with the Before… This summary draws on records from the Singapore Transport Safety Investigation Bureau (TSIB); 8 related events involving the same aircraft type or operator are linked below.

Sourcesthe Singapore Transport Safety Investigation Bureau (TSIB)Primary reportUpdated 2026-09-13Data APIEditorial standards
Airbus A320
Photo: Tosaka / CC BY 3.0, via Wikimedia Commons

On 28 November 2020, a B737-300 freighter (PK-YGW) entered Runway 02C at Singapore Changi Airport without clearance. The aircraft vacated the runway after an alert, and no injuries or damage occurred.

Incident Overview and Aircraft Details On 28 November 2020, a B737-300 freighter operated by Tri MG Intra Asia, registration PK-YGW, was scheduled to depart Singapore Changi Airport for Jakarta Halim Perdanakusuma Airport as Flight TMG019. The aircraft was equipped with two CFM56 3C1 engines. The flight crew consisted of two Captains and a First Officer, with Captain 1 serving as Pilot-in-Command and Pilot Flying, the First Officer as Pilot Monitoring, and Captain 2 as the Augmented Flight Crew Member. Additional personnel on board included a Flight Engineer, a Mechanic, and a Flight Operations Officer. ## Sequence of Events The aircraft pushed back from Bay 304 at 0726LT and was instructed to taxi via Taxiway P, P1, P4, and EP, holding before Taxiway South Cross 1. At approximately 0737LT, the crew was instructed to contact the Runway Controller. The Runway Controller directed the aircraft to continue to holding point E11 and hold short of Runway 02C. The Pilot Monitoring read back the instruction without the words “hold short,” but understood the requirement to hold. The Pilot Flying, however, assumed clearance to enter the runway was granted, particularly as no other traffic was visible on the navigation display. As the aircraft approached Taxiway E11, the Pilot Flying initiated the Before Take-Off Checklist. The aircraft entered Runway 02C at about 0740LT. The Pilot Flying did not notice the red stop bar lights or runway guard lights. The Augmented Flight Crew Member was not monitoring the communications and was unaware that clearance had not been given. ## Detection and Resolution Microwave Barrier Detectors triggered an alert to the Runway Controller when the aircraft crossed the holding position. At that time, another aircraft was on approach to land, approximately three nautical miles from touchdown. The Runway Controller instructed TMG019 to vacate the runway via Taxiway E10. The aircraft exited the runway, and the arriving aircraft landed uneventfully. TMG019 was subsequently cleared for takeoff, and the remainder of the flight was uneventful. ## Safety and Investigation The Transport Safety Investigation Bureau of Singapore classified the occurrence as an incident. There were no injuries to persons on board, and the aircraft sustained no damage. The investigation focused on factors including crew resource management, standard operating procedures, and the communication of taxi instructions. The report emphasized that the sole objective of the investigation was to promote aviation safety, not to apportion blame or liability.

Probable cause

The runway incursion occurred because the Pilot Flying assumed clearance to enter Runway 02C was granted, despite the instruction to hold short, and the Pilot Monitoring did not communicate the holding requirement due to being occupied with the Before Take-Off Checklist.