Tiger Airways Holdings
former Holding Company of airline carriers

Tiger Airways Holdings Limited (SGX: J7X
) was a Singapore-based airline holding company for a group of low-cost carriers operating in the Asia-Pacific region. It was formed in 2007 to allow for easier management of the airline subsidiaries, as well as any future expansion, without having to focus on operational issues, leaving those to the airlines themselves. In 2016, Singapore Airlines purchased the company and it was delisted from the Singapore Exchange.
Group companies
Tigerair (Tiger Airways Singapore)
Tigerair was incorporated on 12 December 2003 and began ticket sales on 31 August 2004. Services commenced on 15 September 2004 to Bangkok. It operates scheduled international services from Singapore Changi Airport and is a wholly owned subsidiary of Tiger Airways Holdings.
In 2006, the airline flew 1.2 million passengers, a growth of 75% from the previous year. The airline was the first to operate from the Budget Terminal in Changi Airport in order to achieve operating-cost savings and its cost structure is modeled after Ryanair. Despite regional competition, the airline has reiterated its current intention to remain focused on flying within a five-hour radius from its Singaporean base.
Following the acquisition of Tiger Airways Holdings by Singapore Airlines, the Tigerair brand was retired with operations merged into Scoot, its sister budget airline.
Begin with the source’s own compact description: “Tiger Airways Holdings” is former Holding Company of airline carriers. The dossier treats that line as a proposition to test through Tiger, Airways and Holdings, not as a finished interpretation.
Why this record matters
The phrase “former Holding Company of airline carriers” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Contemporary correspondence, administrative files and participant testimony can test how later narratives organized the event or institution. The source revision retrieved here is dated Sep 26, 2026. The linked authority identifier is Q7801370. 2 of 2 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 2007, 2016, 2003 and 2004.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. 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
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Tiger Airways Holdings”, its source revision and the description used here.
- Expand the search: follow Tiger Airways Holdings primary sources, Tiger Airways Holdings archive and Tiger 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 “Tiger Airways Holdings”?
- What chronology connects this entry to wider political or social change?
- Who created the surviving record, and for what administrative purpose?
Search terms from this dossier
This entry incorporates text from “Tiger Airways Holdings” 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.