GippsAero GA8 Airvan
single engine shoulder-wing utility aircraft
The GippsAero GA8 Airvan is a single-engined utility aircraft manufactured by GippsAero (formerly named Gippsland Aeronautics) of Victoria, Australia. It can seat up to eight people, including the pilot.
The GA8 has been designed for use in remote areas and from austere air strips, performing tasks such as passenger services, freight, sightseeing, parachuting, observation, and intelligence, surveillance and reconnaissance (ISR) and search and rescue operations. Its design emphasises ruggedness and ease of use. First flown on 3 March 1995 and type certified under Federal Aviation Administration (FAA) Part 23 requirements during summer 2004, the GA8 has been flown by a diverse range of operators throughout the world.
Since its introduction, improved models featuring more powerful engines have been introduced; an enlarged turboprop-powered derivative, designated as the GippsAero GA10, has been developed. A floatplane model of the GA8 has also been produced. At EAA Oshkosh 2014, the GA8 Airvan was officially renamed as the Mahindra Airvan 8 as a reflection of GippsAero's recent acquisition by Indian conglomerate Mahindra Group. The aircraft was produced in Australia; establishment of a North American final assembly line to produce the type was proposed at one time.
In November 2020, Mahindra Aerospace, which had purchased the company, announced that production would cease at that time, citing the financial effects of the global economic slowdown due to the COVID-19 pandemic.
This brief starts where responsible research should: with the source description of “GippsAero GA8 Airvan” as single engine shoulder-wing utility aircraft. 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 single engine shoulder-wing utility aircraft. Its deeper value depends on whether names, dates, institutions and citations support that framing.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Aug 11, 2026. The linked authority identifier is Q747706. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1995, 2004, 2014 and 2020.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. 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 “GippsAero GA8 Airvan”, its source revision and the description used here.
- Expand the search: follow GippsAero GA8 Airvan primary sources, GippsAero GA8 Airvan archive and GippsAero 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 “GippsAero GA8 Airvan”?
- 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 “GippsAero GA8 Airvan” 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.