No aliases recorded.
Included from Wikipedia – List of ships at Dunkirk . These collection pages contain a matching vessel-name reference.
…CAP D'ANTIFER( 1) French cargo vessel 31st May 0550 Sailed from Dover for Dunkirk in company with the cargo ships Ingenieur Cachin, Emma and Francois Tixier, and escorted by the patrol 1200 vessel Reine des Flots. Arrived Dunkirk [and apparently unloaded munitions There is no further informat…
…o May vessel (1) 31st May 0550 Sailed from Dover to Dunkirk, escorted by the patrol vessel Reine des Flots; in company were the cargo ships Cap D'Antifer, Francois Tixier and Emma. 1200 Arrived Dunkirk [and apparently unloaded munitions]. There is no further information, but D.R. states that…
…and A Steamer No Gustave Denis Drifter Guidel British (if L/L Sweep. Wastwater A D (armed) decision suitable) Cape Warwick A Windermere A D Cap D'Antifer Patrol British Le Tiger AD At Southampton. Boat Auxiliary Portsmouth. Patrol Ullswater A D Portland Chasse Maree Trawler British L/L Sweep.…
…Reine Des Flots (Enseigne de vaisseau Le Bitoux) 1,312 Sauternes (escort vessel) Total 2,504 CARGO SHIPS3. Total 12, of which 2 were sunk. Cap d'Antifer Cap Tafalneh 291 Cérès Douaisien Emma Fronsac 29 Frangois Tixier 500 Ingénieur Cachin Margauz 601 Monique Normanville Schiaffino 369 - St.…
Help complete the archive
Contribute photographs of CAP D'ANTIFER to the archive for editorial review. Submissions remain private and will only be published following approval by an administrator.
Already have an account? Log in before uploading to link new photographs immediately.
1 potential matching record has been identified.
These records may contain vessel particulars, reported movements, participation assessments, named personnel and source references. A match does not by itself prove that the vessel participated in Operation Dynamo.
“Potential match” means a candidate returned by one or more indexing rules; it is not necessarily an exact identity match. Depending on the source, matching may use a normalised vessel name, a partial text or OCR hit, an alias, or related metadata. Roman-numeral suffixes such as I, II, III, IV and V may be absent, misread or separated from the base name, so records for similarly named vessels can be grouped incorrectly. Multi-word names can also produce candidates where only one significant word matches. Confirm the full name, numeral, vessel type, dimensions, builder, ownership, dates and source context before treating two records as the same vessel.
We are compiling and checking transcriptions, metadata, vessel-name matches, source references and reuse permissions before publishing further detail. This work helps prevent incomplete OCR, historic spelling variations or unverified associations from being presented as established fact.
Account registrations and access to these developing records are temporarily unavailable. Existing account holders may log in, and everyone can join the newsletter for publication updates.
1 potential matching record has been identified.
These records may contain service-list entries, vessel metadata, source-page references and protected full-size document images. A match does not by itself prove that the vessel participated in Operation Dynamo.
“Potential match” means a candidate returned by one or more indexing rules; it is not necessarily an exact identity match. Depending on the source, matching may use a normalised vessel name, a partial text or OCR hit, an alias, or related metadata. Roman-numeral suffixes such as I, II, III, IV and V may be absent, misread or separated from the base name, so records for similarly named vessels can be grouped incorrectly. Multi-word names can also produce candidates where only one significant word matches. Confirm the full name, numeral, vessel type, dimensions, builder, ownership, dates and source context before treating two records as the same vessel.
We are compiling and checking transcriptions, metadata, vessel-name matches, source references and reuse permissions before publishing further detail. This work helps prevent incomplete OCR, historic spelling variations or unverified associations from being presented as established fact.
Account registrations and access to these developing records are temporarily unavailable. Existing account holders may log in, and everyone can join the newsletter for publication updates.
A source-page icon is available. Sign in to view the indexed details and protected full-size image.
1 potential matching record has been identified.
These records may contain OCR text matches, source files, page references and digitised page imagery. A match does not by itself prove that the vessel participated in Operation Dynamo.
“Potential match” means a candidate returned by one or more indexing rules; it is not necessarily an exact identity match. Depending on the source, matching may use a normalised vessel name, a partial text or OCR hit, an alias, or related metadata. Roman-numeral suffixes such as I, II, III, IV and V may be absent, misread or separated from the base name, so records for similarly named vessels can be grouped incorrectly. Multi-word names can also produce candidates where only one significant word matches. Confirm the full name, numeral, vessel type, dimensions, builder, ownership, dates and source context before treating two records as the same vessel.
We are compiling and checking transcriptions, metadata, vessel-name matches, source references and reuse permissions before publishing further detail. This work helps prevent incomplete OCR, historic spelling variations or unverified associations from being presented as established fact.
Account registrations and access to these developing records are temporarily unavailable. Existing account holders may log in, and everyone can join the newsletter for publication updates.
These details have been aggregated from multiple sources and may include contemporary records, later recollections, claims or assertions for which no corroborating evidence has been identified. Inclusion does not establish that any account or assertion is accurate. The information may be incomplete, out of date, disputed or incorrect and should be checked against the underlying source records and independent evidence before being relied upon.
No additional ship details available.
Source: Lloyd’s Register Foundation, Heritage & Education Centre, Lloyd’s Register of Yachts 1939, digitised via Internet Archive. Licensed under CC BY-NC-SA 4.0. Images have been converted, resized and watermarked for web display; machine-generated table OCR has been added.
No Lloyd’s records.
Imaged document collections containing pages whose OCR text or table data has been tagged with the name CAP D'ANTIFER. Open a collection to view the page images and transcriptions.
Contains public sector information licensed under the Open Government Licence v3.0.
| 31st May | 0550 | Sailed from Dover |
| for Dunkirk in company with the cargo ships | ||
| Ingenieur Cachin, Emma and Francois Tixier, and escorted by the patrol vessel Reine des Flots. | ||
| 1200 | Arrived Dunkirk [and apparently unloaded munitions | |
| Lost | ||
| all | ||
| 0400 | ||
| 1000 | ||
Contains public sector information licensed under the Open Government Licence v3.0.
INGENIEUR CACHIN French cargo May vessel (1) 31st May 0550 Sailed from Dover to Dunkirk, escorted by the patrol vessel Reine des Flots; in company were the cargo ships Cap D'Antifer, Francois Tixier and Emma. 1200 Arrived Dunkirk [and apparently unloaded munitions]. There is no further information, but D.R. states that troops were landed in England as follows: On 31st May, 600, by the "Cachin". On lst June, 1, by the Ingenieur Cachin. Total 601 Ingrien Cachin X 24 Lieutenaut de vaitreau Helie was an auxiliary minalayer. She disemBarKed 1 778 solder's of the French Cavalry Corpse in Le Havre 1st june 21 30. Note by Cdr. Cras of French Historical Section (1) Also referred to as an auxiliary minesweeper. 57
Source: The National Archives, Kew, RED LIST INDEX 1939 40. Contains public sector information licensed under the Open Government Licence v3.0.
| Group. | Station. | Name of Ship. | Group. | Station. | Name of Ship |
| 10th A/S Striking Force. | Aberdeen | Thirlmere A D Buttermere A D | 17th A/S Striking Force. | Aberdeen | Coventry City AD Cape Portland A |
| Wastwater A D | Cape Warwick A | ||||
| Windermere A D | Le Tiger AD | ||||
| Portland | Ullswater A D Ellesmere AD | 18th A/S Striking Force. | Belfast | King Sol A D (S.O.) St. Elstan A | |
| 11th A/S Striking Force. | Belfast | Cape Comorin AD Ayrshire A D | Portland | Loch Monteith A D St. Cathan A | |
| 12th A/S Striking Force. | Belfast | Northern Spray A D Northern Pride A D | 19th A/S Striking Force. | Aberdeen | Wistaria AD Whitethorn A |
| Northern Gem A D Northern Dawn A D Northern Wave A D | 20th A/S Striking Force. | Elm D Hazel D | |||
| 14th A/S Striking Force. | Aberdeen | Scottish A D (S.O.) Imperialist A Loch Oskaig A D Alouette A D | 21st A/S Strik- ing Force. | Ports- mouth Belfast | Daneman AD (S.O.) Wellard AD Lady Elsa AD Man-o'-War AD |
| 15th Force. A/S Striking | Belfast | St. Kenan A D St. Loman A D | Belfast | St. Apollo St. Zeno | |
| 16th Force. A/S Striking | Belfast | Angle A D Arab AD | Harwich | St. Madeline St. Lilian |
Source: The National Archives, Kew, ADM 234 360. Contains public sector information licensed under the Open Government Licence v3.0.
| Cap d'Antifer |
Movements recorded for CAP D'ANTIFER during the evacuation period, as plotted on the Operation Dynamo map.
No reviewed movement log is currently published for this vessel.
Log in to suggest an evidence-backed edit or a new movement log.
Documents and descriptions supplied by registered researchers. All submissions are reviewed in accordance with our Terms and Conditions.
No user-contributed documents have been approved for this vessel yet.
Log in to contribute a document and description.