Fokker F28 Fellowship
twin-engined jet airliner family 1967

The Fokker F28 Fellowship is a twin-engined, short-range jet airliner designed and built by Dutch aircraft manufacturer Fokker.
Following the Fokker F27 Friendship, an early and commercially successful turboprop-powered regional airliner, Fokker decided to embark on developing a new turbofan-powered commuter aircraft that would build upon its experiences with the F27. During the design phase, a high level of attention was paid to market research and operator concerns; amongst other changes made, the prospective jetliner was increased in size, changing its maximum seating capacity from 50 to 65 passengers. During April 1962, Fokker announced the formal launch of the F28 Fellowship. The Fokker F28 directly competed with the American Douglas DC-9 and British BAC 1-11.
On 9 May 1967, the prototype F28-1000 conducted its maiden flight. On 24 February 1969, Kees van Meerten, Fokker Board member, received the Certificate of Airworthiness from Willem Jan Kruys, Director General of the Dutch National Aviation Authority. The first revenue-earning flight by Braathens was performed on 28 March 1969. Following its entry to service, Fokker developed multiple variants of the F28; one model, the F28-2000, featured an extended fuselage that could accommodate up to 79 passengers. A major revision was the F28-4000, which was powered by quieter Rolls-Royce Spey 555-15H engines, a redesigned cockpit, and a modified wing, and had a further increased seating capacity up to 85 passengers.
“Fokker F28 Fellowship” enters the record as twin-engined jet airliner family 1967. Crown Archives preserves that source wording while asking what Fokker, Fellowship and twin-engined can confirm, complicate or overturn.
Why this record matters
“Fokker F28 Fellowship” is worth following because a concise public description often conceals a longer documentary argument. Here, Fokker, Fellowship and twin-engined provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 21, 2026. The linked authority identifier is Q725319. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1962, 1967, 1000 and 1969.
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 “Fokker F28 Fellowship”, its source revision and the description used here.
- Expand the search: follow Fokker F28 Fellowship primary sources, Fokker F28 Fellowship archive and Fokker 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 “Fokker F28 Fellowship”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Fokker F28 Fellowship” 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.