EFTA00005994: Monthly Route Calendars From January 2017 Through June 2019

Snapshot

---

What Is This Record?

EFTA00005994 is a 31 page file in the Justice Department’s Epstein release. Its substantive travel material consists of one calendar page for every month from January 2017 through June 2019. Colored cells contain short entries beginning with “Outbound” and “Inbound,” followed by airport codes, place names or the word “Unknown.” The file offers a compact index of route assertions that can be checked against other records. It does not supply the underlying source for each assertion.

The opening page requires separate treatment. PDF page 1, EFTA00005994 says “ITEM WAS NOT SCANNED” and carries the handwritten description “Refresh Eye Drops.” The following page begins the January 2017 calendar. Nothing in the visible packet explains why the item form and the calendars appear together. The form is therefore retained as part of the file inventory, without presenting it as a calendar title page or assuming that the described item has a travel connection.

---

Key Takeaways

• The calendar sequence is complete for the 30 displayed months, but that does not make the record a complete travel history. Blank cells and missing return labels cannot establish where an aircraft or a person was on those dates.
• The most repeated printed routes are TIST to TEB and PBI to TIST, with 21 labels each. TEB to France appears 19 times. These counts preserve repeated adjacent dates and do not resolve whether every label describes a separate completed journey.
• Six legs have an “Unknown” endpoint. France, Morocco, Canada, British VI, St Barthelemy and Dom Rep appear as place labels without a specific foreign airport code.
• Several source features need caution: identical routes on adjacent dates, multiple legs in one cell, colored bands spanning otherwise unlabeled dates, and a discontinuity in the March 8, 2017 cell.
• The calendars do not name a passenger, aircraft or compiler. They cannot alone place Jeffrey Epstein, an associate or any survivor aboard a flight or at a destination.

---

Source and Provenance

The Justice Department’s Data Set 4 listing includes EFTA00005994.pdf. The official PDF location and Epstein Data record are the direct source references for this article. The 31 page copy reviewed carries a continuous Bates sequence from EFTA00005994 to EFTA00006024. The review used the supplied PDF’s page images, not an archive’s automated summary, to read the dates and routes.

The public release location establishes where the file is listed. It does not supply a complete chain of custody for the calendar content. The reviewed pages do not identify the original compiler, source database, calendar owner, aircraft, case number, signature or method used to select the entries. No native calendar file, spreadsheet or supporting row level records accompany the supplied PDF.

Three kinds of dates should remain separate. The month headings and numbered cells supply the calendar dates. The first page’s footer supplies a July 27, 2020 revision date for the item form. Neither establishes when the route calendars were compiled, when this exact packet was assembled, or when it first became public. The DOJ download presented an age verification page during this review; the supplied PDF was the accessible copy inspected in full.

---

What the Record Contains

The calendars use a Sunday through Saturday grid, a month heading, colored route cells and an Airport Codes legend. Some pages carry annual numbering such as “Page 2 of 12.” Those labels refer to the calendar layout and must not be substituted for the PDF’s total of 31 pages. The final month in this file is June 2019; no July through December 2019 calendar pages are included.

---

Evidence Appearances and Location Labels

The relevant appearances in this record are location labels and route codes rather than named people. The following table preserves the meanings printed in the calendar legends. A broad place label is not expanded into a specific airport, property or meeting location.

There is no visible named passenger list or aircraft identification to connect these entries to a particular traveler. The word DocLab appears on the opening form’s footer; that is a form label, not evidence identifying the calendar compiler.

---

How to Read the Calendar Entries

Each ledger row below corresponds to one printed origin and destination pair. “Outbound TIST, Inbound TEB” is rendered as TIST → TEB for readability. An arrow preserves the stated direction; it does not certify that an aircraft departed or arrived. Dates are taken from the cell containing the route text, not from every day touched by a colored background.

• When a cell prints two route legs, both are recorded separately. The February 19, 2019 cell, for example, prints TIST → Dom Rep and Dom Rep → PBI.
• When the same route is printed on two dates, both source assertions are retained. They are not silently merged, corrected or counted as one confirmed trip.
• A colored band with only one route label contributes one label, even if the color extends across several dates or onto the next month.
• Unlabeled cells contribute no route label. They are not coded as a stay, a cancellation, a missing flight or proof that no travel occurred.
• Color is recorded descriptively where useful. The packet supplies no color key explaining whether a shade represents direction, duration, status, aircraft, source type or another classification.

This method produces 124 route legs on 110 distinct dates. The distinction matters because more than one leg can appear on a date. It also avoids turning a long colored bar into a series of invented daily flights.

---

Route Patterns and Timeline Significance

The pattern is concentrated in a small set of repeated labels. TIST appears as an endpoint in 79 of the 124 printed legs, TEB in 64 and PBI in 40. France appears in 36. These figures count a route once for each endpoint it contains; they are not passenger totals, visits, days spent in a place or aircraft utilization statistics.

The two directions of a route need not balance. TEB → France appears 19 times, while France → TEB appears 13 times and France → KISP appears three times. PBI → France appears once. Those differences cannot be resolved by inventing return legs or treating every outward entry as the start of a fully documented round trip.

The 2017 sequence contains 51 legs on 46 dates, the 2018 sequence contains 54 legs on 46 dates, and January through June 2019 contains 19 legs on 18 dates. June 2017 and December 2018 each contain only one printed route, but neither is a blank month. January 2019 contains five legs. The numbers describe the density of this calendar, not a measured rise or fall in anyone’s actual travel.

The calendar dates place the material in 2017 through the first half of 2019. They do not make the packet evidence of a 2004 event, and the July 2020 form revision does not extend the travel period. The record ends without a complete return sequence: its final printed route is TEB → France on June 14, 2019, on PDF page 31, EFTA00006024. No later journey should be supplied from assumption.

---

Complete Monthly Route Ledger

The source PDF is the authority for this ledger. Every displayed month and all 124 leg labels are included below. Each month heading supplies its PDF page and Bates stamp. Color notes document unusual presentation; they do not assign meaning to the colors. Repeated routes and discontinuities are preserved as printed.

2017

January 2017. PDF page 2, EFTA00005995. 5 printed legs.

February 2017. PDF page 3, EFTA00005996. 5 printed legs.

March 2017. PDF page 4, EFTA00005997. 8 printed legs.

April 2017. PDF page 5, EFTA00005998. 6 printed legs.

May 2017. PDF page 6, EFTA00005999. 4 printed legs.

June 2017. PDF page 7, EFTA00006000. 1 printed leg.

July 2017. PDF page 8, EFTA00006001. 5 printed legs.

August 2017. PDF page 9, EFTA00006002. 2 printed legs.

September 2017. PDF page 10, EFTA00006003. 2 printed legs.

October 2017. PDF page 11, EFTA00006004. 3 printed legs.

November 2017. PDF page 12, EFTA00006005. 5 printed legs.

December 2017. PDF page 13, EFTA00006006. 5 printed legs.

2018

January 2018. PDF page 14, EFTA00006007. 6 printed legs.

February 2018. PDF page 15, EFTA00006008. 4 printed legs.

March 2018. PDF page 16, EFTA00006009. 6 printed legs.

April 2018. PDF page 17, EFTA00006010. 5 printed legs.

May 2018. PDF page 18, EFTA00006011. 3 printed legs.

June 2018. PDF page 19, EFTA00006012. 5 printed legs.

July 2018. PDF page 20, EFTA00006013. 4 printed legs.

August 2018. PDF page 21, EFTA00006014. 6 printed legs.

September 2018. PDF page 22, EFTA00006015. 5 printed legs.

October 2018. PDF page 23, EFTA00006016. 4 printed legs.

November 2018. PDF page 24, EFTA00006017. 5 printed legs.

December 2018. PDF page 25, EFTA00006018. 1 printed leg.

2019

January 2019. PDF page 26, EFTA00006019. 5 printed legs.

February 2019. PDF page 27, EFTA00006020. 3 printed legs.

March 2019. PDF page 28, EFTA00006021. 3 printed legs.

April 2019. PDF page 29, EFTA00006022. 4 printed legs.

May 2019. PDF page 30, EFTA00006023. 2 printed legs.

June 2019. PDF page 31, EFTA00006024. 2 printed legs.

---

Source Anomalies and Missing Connections

Several details are important enough to retain outside the ledger. They show why a route calendar should be examined as a source rather than converted automatically into a seamless itinerary.

---

What the Record Does and Does Not Prove

What it establishes: the reviewed PDF contains dated route assertions, a continuous monthly sequence, visible location labels and an item form. The page images support the transcription, the page inventory and the counts in this article. They permit comparisons with other records by date and stated direction.

What it does not establish: the calendars alone do not show that every entry became a completed flight, that a particular aircraft operated it, or that Jeffrey Epstein or anyone else was aboard. They do not establish passenger numbers, crew identity, arrival or departure time, time zone, purpose, meeting attendance, property visits, wrongdoing or a complete travel history.

A TIST label cannot establish onward travel to Little Saint James. A France label cannot establish a visit to a Paris apartment. A route to an airport or a broad geographic label is not a record of everyone who may have used that route. Similarly, an omitted route cannot establish an alibi or prove that travel never occurred.

The unresolved provenance is also material. Without an identified compiler and supporting records, the review cannot determine whether the calendars summarize planned trips, reported movements, completed flights, a mixture of sources or selected events. The wording “printed route” is used throughout for that reason.

---

Related Evidence and Sleuth Reporting

Greg Conners’s October 23, 2026 report, “Epstein’s Disappearing Helicopters,” concerns a different set of aviation records: FAA correspondence naming spreadsheets and questions about passenger information and onward travel. It is relevant to the method of reading a route calendar because it distinguishes aircraft movement records from the separate question of who was aboard or where a traveler went after landing. His report does not authenticate EFTA00005994, identify its compiler or fill its gaps.

EpsteinWiki’s review of Conners’s reporting provides a separate guide to those records. It should not be read as proof that the spreadsheet trail and this calendar came from the same source. No attempt is made here to import passenger identities or disputed claims from that investigation into this ledger.

The next useful comparison would match each printed date and route with an independently sourced record carrying an aircraft registration, time, origin, destination and, where lawfully available, passenger information. Any mismatch would need to preserve both records and their different purposes. A broad similarity in route or month would not be enough to establish a match.

---

Reliability and Limitations

The source images contain more information than the PDF’s extracted text reliably captures. Some text inside blue, green or red cells is absent or distorted in the OCR layer. The visual grid is also essential for assigning a route to the correct date. The ledger therefore follows the page images rather than treating an extracted text sequence as a dated itinerary.

The calendar sequence has no missing month within its displayed period, and the Bates stamps run consecutively. That is a statement about this PDF’s structure. It is not proof that all relevant supporting material was released, that every route was recorded, or that no other version exists. The unexplained opening form and lack of compiler attribution remain provenance limitations.

The count of 124 legs is reproducible from the printed labels using the stated method, but it deliberately includes repeated adjacent dates. It should not be presented as a count of 124 distinct, completed flights. Likewise, 110 dates does not mean 110 travel days for a particular person. The route table describes what this record says, not an independently reconstructed movement history.

---

Survivor Safety and Privacy

The reviewed route calendars do not provide named passengers or crew. This article does not try to identify travelers through adjacent records, infer a survivor’s identity, or connect an unnamed person to a particular route. The first page’s item description is treated only as visible document text and is not attributed to anyone’s medical history. No personal contact details, private addresses or sensitive identifiers are required to explain the file.

---

Verification and Source Review

The review covered all 31 supplied PDF pages, including the item form, every calendar month, the route cells, legends and Bates stamps. Routes and dates were checked against rendered page images. The ledger was then counted by leg, distinct date, month, year and route pair. The page sequence and the arithmetic were checked separately from any claim that travel actually occurred.

The source search checked the exact document identifier, the official Data Set 4 listing, the official download location and the Epstein Data viewer. Relevant aviation reporting was read for methodological context. Search results from other document mirrors and automated research summaries were treated as discovery aids, not as independent confirmation of dates, passenger identities, color meanings or completeness.

This is an exhaustive page inventory and route transcription of the supplied EFTA00005994 file, not a claim to have read every Epstein file or reconciled every route against the full released corpus. No native calendar, complete supporting flight file, passenger manifest or compiler testimony was available for this review. No independently verified international report was used to assign a more specific foreign airport or traveler to the broad labels in the calendar. Source review date: October 30, 2026.

---

Related EpsteinWiki Pages

• Flights & Travel: Tools and Verification Guide explains the difference between locating a travel record and verifying what it supports.
• EFTA01683110: Aircraft Arrival, Registration and Immigration Records covers a different packet whose record types should not be conflated with these calendars.
• Government Exhibit 662 RR is a separate guide to the pilot log exhibit, not a substitute source for the entries transcribed here.
• Greg Conners and the Helicopter Spreadsheet Lead discusses a separate records retrieval question.

---

Conclusion

EFTA00005994 is useful because it gathers 30 months of dated route labels into one readable sequence. A full visual transcription recovers entries that text extraction can miss and exposes repetitions, uncertain endpoints and gaps that a simplified itinerary would hide. Its value is as a precisely cited route index. Establishing who traveled, on which aircraft and for what purpose requires other evidence.

---

Questions and Answers

What Is EFTA00005994?

EFTA00005994 is a 31 page PDF listed in DOJ Data Set 4. It begins with an item not scanned form and then contains 30 monthly route calendars covering January 2017 through June 2019.

How Many Flights Does It Record?

The visual transcription contains 124 printed route legs on 110 dates. That is not a verified flight total. Multiple legs can share a cell, some routes repeat on adjacent dates, and the file does not confirm completion.

Does It Show Jeffrey Epstein Was on Every Route?

No. The reviewed calendars do not name passengers or identify an aircraft. A route label alone cannot place Epstein, an associate or a survivor aboard.

Why Is the First Page About an Item That Was Not Scanned?

PDF page 1, EFTA00005994, is a form bearing that notice and the handwritten description “Refresh Eye Drops.” The file does not explain its relationship to the calendars. It is not treated as their title page.

Do the Colors Explain the Type or Length of a Trip?

No color key is supplied. A long band can span several dates with only one label, and June 2019 contains two labels on one continuous yellow bar. Color alone cannot establish a daily flight or a stay.

Is January 2019 Blank?

No. PDF page 26, EFTA00006019 contains five route labels: January 6, 8, 16, 22 and 30. Reading only the extracted text can miss content inside colored cells.

Does France Mean Paris, and Does TIST Mean Little Saint James?

The record supplies France as a broad label and defines TIST in its legend as “US Virgin Island.” It does not document a particular French airport, a Paris property visit or an onward transfer to a private island.

Does This File Establish Anything About a 2004 Event?

The calendar period is January 2017 through June 2019. The file does not supply a 2004 calendar or evidence establishing a 2004 event. A similar name or research topic in another file would not change this document’s dates.

Where Can the Entries Be Checked?

Use the Justice Department PDF or Epstein Data document viewer. The monthly ledger gives both the PDF page number and the stamped Bates identifier. The official download may require age verification.

What Would Be Needed to Confirm a Particular Journey?

An independently sourced record matching the date, direction and aircraft would strengthen a route comparison. Passenger presence and onward travel would still require their own evidence. This packet alone does not provide those links.

---

Sources

• EFTA00005994, Epstein Data Document Viewer. Direct record anchor for the file reviewed; analytical summaries are not used as primary proof.
• EFTA00005994.pdf, United States Department of Justice. Official download location. PDF pages 1 through 31, Bates EFTA00005994 through EFTA00006024. The supplied copy’s images are the basis for the ledger.
• Data Set 4 Files, United States Department of Justice. Official index listing the exact PDF filename.
• Greg Conners, “Epstein’s Disappearing Helicopters,” October 23, 2026. Related aviation records reporting used only for the distinction between route information, passenger evidence and onward travel. It is not a source for the calendar transcription.