TransAsia Airways Flight 235
2015 plane crash of a TransAsia Airways ATR 72-600 in Taipei, Taiwan

TransAsia Airways Flight 235 was a domestic flight from Taipei to Kinmen, Taiwan. On 4 February 2015, the aircraft serving the flight, a 10-month-old ATR 72, crashed into the Keelung River around 5 km (3.1 mi; 2.7 nmi) from Taipei Songshan Airport, from where the aircraft had just departed. On board were 58 people, 15 of whom survived with injuries.
Two minutes after takeoff, the pilots reported an engine failure. After climbing to a height of 1,630 ft (500 m), the other engine, still operating normally, was mistakenly shut down. The aircraft lost altitude, banked sharply to the left and clipped a taxi traveling west on the Huandong Viaduct (causing injuries to two more persons), then the viaduct itself, before crashing into the river below.
Flight 235 was the second fatal accident involving a TransAsia Airways ATR aircraft within seven months; Flight 222 had crashed on 23 July 2014, also with 58 people on board. On that flight, 48 people had died.
Flight
Flight 235 departed Taipei Songshan Airport at 10:52 Taiwan time (02:52 UTC), for its destination of Kinmen Airport, with 53 passengers and five crew members on board. Shortly after take-off, a fault in the autofeather unit of the number-2 engine caused the automatic take-off power control system to autofeather that engine.
This brief starts where responsible research should: with the source description of “TransAsia Airways Flight 235” as 2015 plane crash of a TransAsia Airways ATR 72-600 in Taipei, Taiwan. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as 2015 plane crash of a TransAsia Airways ATR 72-600 in Taipei, Taiwan. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 18, 2026. The linked authority identifier is Q18951344. Authority coordinates are 25.063, 121.618. None of the 1 selected statements returned an explicit reference. The first chronological checks are 2015 and 2014.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “TransAsia Airways Flight 235”, its source revision and the description used here.
- Expand the search: follow TransAsia Airways Flight 235 primary sources, TransAsia Airways Flight 235 archive and TransAsia research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “TransAsia Airways Flight 235”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “TransAsia Airways Flight 235” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.