China.Hangzhou Airport (UFO shutdown)

Around 8:40 PM on 7 July 2010, according to ABC News, the crew of a flight preparing for descent into Hangzhou's Xiaoshan International Airport (Zhejiang province) detected an unidentified object and notified air traffic control. Within minutes, aviation authorities grounded outbound flights and diverted inbound ones to the airports of Ningbo and Wuxi: 18 flights were affected (more than 20 delayed by 56 minutes, according to Beijing Review) and operations returned to normal about an hour later. According to ABC, Hangzhou residents said that less than an hour before the closure they saw a flying object emitting red and white rays of light. For a country where an airport closure is major news, the episode had enormous media impact, and it was part of a run of reported sightings in China that summer.

Several photographs circulated, but they were not from the time of the closure: Hangzhou residents released images taken in the afternoon of an object bathed in golden light with a comet-like tail, which the city's meteorological authorities attributed to sunlight reflecting off an airplane, and a resident, Ma Shijun, photographed at 8:26 PM a streak of white light that, according to Beijing Planetarium curator Zhu Jing, looks just like a plane shining its strobe lamps; Ma himself told Xinhua he did not know whether it was a plane or the airport's object. According to later summaries not checked against sources of the time, the investigation was joint between the Civil Aviation Administration of China (CAAC) and the regional military command's air force; the head of CAAC air traffic control in Zhejiang, Wang Jian, told Xinhua that 'no conclusion has yet been drawn', and the reports consulted mention no radar return from the object. No closed official explanation was published, and the ones the press gave contradict each other: on 5 August China Daily blamed the closure on a 'black flight', a private plane or helicopter flying without authorisation, and later the South China Morning Post reported that it was due to a military test at a nearby air force base. An investigation group from the Beijing UFO Research Society and the Shanghai UFO Research Center visited the airport on 14 July and on the 25th concluded that there was no evidence of an alien craft, but that private or military aircraft activity could not be ruled out; no reading was officially confirmed.

The case should be read for what it is and is not. What is solid and verifiable is institutional: the airport did close and there was a documented operational response with flight figures. The anomalous part (the 'object') is much weaker: the most circulated images are not from the time of the closure and were attributed to aircraft, and the reports provide no instrumental record of the object. Hangzhou stands as a reference case for China (a huge, opaque country on the matter) and, at the same time, as a good example of how a real event (the closure) and fragile evidence (the photo) combine in public perception.

Hangzhou matters for two almost opposite reasons. On one hand, it opens a window onto China: the world's most populous country, with an opaque state apparatus, yields few verifiable cases, and this one (by the magnitude of the airport closure and its coverage) is the most institutionally solid. On the other, it is a reminder of discipline: a real operational event (closure, diverted flights) does not make the visual evidence anomalous, which here is weak and consistent with prosaic explanations. That asymmetry defines it (strong institutional response, weak object), with the explicit caution that 'they closed the airport' is not the same as 'there was a craft'. The file is also a good reminder of how informational opacity manufactures mystery: in a system where military activity and investigation details are not published, official silence is read as confirmation of something extraordinary, when the published hints themselves point to a conventional cause (an unauthorised flight or a military test) that simply was never publicly clarified. The file's caution does not deny that something triggered the closure; it denies that that something should be read as anomalous.