Banu Kolukkoylu

Snapshot
| Field | Documentary detail |
|---|---|
| Name indexed | Banu Kolukkoylu is the retained index label; the reviewed log does not establish that exact surname spelling or a biographical identity. |
| Retained table window | March 15 through September 9, 2001; this is the span of the 26 retained rows, not a verified travel history for one identified person. |
| Primary evidence | EFTA02846460, pages 80–86; date and route checks are separate from passenger identification. |
| Verification requirement | Two rows show Banu with an uncertain handwritten surname; six show BK only; eighteen have passenger-field redactions without visible Banu/BK confirmation. |
This page retains a 2001 flight-index inventory under the label Banu Kolukkoylu. The dated routes can be located in the original log, but the passenger evidence differs: two rows show Banu followed by a handwritten surname whose exact spelling is uncertain, six show BK only, and eighteen contain passenger-field redactions without visible Banu/BK confirmation. These records do not establish that all 26 rows concern one identified person or that an indexed passenger boarded.
Key Takeaways
- The table retains 26 indexed rows. The current index result was not reproduced in this review; the original log supports their dated routes with differing levels of passenger visibility.
- A December 2002 shipping record visibly contains Banu Kucukkoylu. The separately cited travel-agency and civil-disclosure pages remain unverified in this review, and similar names do not establish that the records concern the same person.
- Judge Preska expressly rejected the Doe 102 identification in January 2024.
What the Documents Reveal
The inventory below contains 26 dated routes, all located in the reviewed log pages. That count is not a verified count of journeys by Banu: initials do not identify a person, redacted passenger fields remain unknown, and a manifest entry does not prove boarding. Earlier claims that different indexes returned 24 and 26 appearances have not been reconciled against a preserved, reproducible search. Do not merge the index label with similarly spelled shipping, litigation or public-biography names without independent identification.
The retained March 15 routes run from Teterboro to Islip, Lake City and Palm Beach; March 16 continues through Miami to St. Thomas. Later dated rows include March 29 Teterboro–Santa Fe and summer routes through Teterboro and Westchester. These are route observations, not proof that the same identified passenger took every leg. The original log uses TIST on the rows presented here as STT. No passenger name, initial, shared manifest or redaction establishes knowledge of abuse or involvement in recruitment.
The Primary Flight Log and Its Limits
EFTA02846460 is a handwritten aviation-log collection whose cover is marked Government Exhibit 662-RR and states that it was publicly released in U.S. v. Maxwell. Pages 80–86 are the primary anchor for this inventory. The entries record dates, routes, aircraft identifiers as written, and passenger names, initials or redactions. An aircraft notation is not an independently checked registration history, and a listed passenger is not proof of boarding, a meeting or a shared purpose. The exhibit label alone does not establish what testimony explained each entry.
Researchers should distinguish a handwritten entry from a later schedule, OCR transcription or online index. The reviewed pages of EFTA02796838 are compiled flight schedules filed as an exhibit in Giuffre v. Maxwell, Document 153-2, on May 11, 2016. Relevant passenger fields in those schedule copies are redacted; their dates and routes are not independent confirmation of the indexed passenger’s identity. Reproductions and transcriptions of one entry must not be counted as separate journeys.
Retained Flight-Index Inventory
The following table preserves 26 rows previously attributed to Epstein Data’s flight finding aid. The earlier October 14, 2026 search was not reproduced in this review, so its claimed completeness remains unverified. Every retained date and route was matched to an entry in the original log. The passenger evidence is reported separately in each row; this is not a count of 26 verified flights by one identified person.
The source column gives the original log page, trip number and visible passenger evidence. BK remains an unexplained initial pair; redacted fields are not reconstructed. Earlier index-linked references are retained as research leads, not independent passenger confirmation. Where this table uses STT, the corresponding log writes TIST. Multiple labels, copies or compiled schedules may refer to one entry.
| Indexed date | Airport codes | Source provenance and verification limit |
|---|---|---|
| 2001-03-15 | TEB to ISP | Original log p. 80, trip 1471: date and route present. Banu is legible; the exact handwritten surname is uncertain. Filed schedule p. 25 also contains the dated route, with redacted passenger fields. Earlier index-linked references, not independent passenger confirmation: EFTA02796838; EFTA02727228. |
| 2001-03-15 | ISP to LCQ | Original log p. 81, trip 1472: date and route present. Banu is legible; the exact handwritten surname is uncertain. Filed schedule p. 25 also contains the dated route, with redacted passenger fields. Earlier index-linked references, not independent passenger confirmation: EFTA02727229. |
| 2001-03-15 | LCQ to PBI | Original log p. 81, trip 1473: date and route present. BK only; the initials do not establish identity. Filed schedule p. 25 also contains the dated route, with redacted passenger fields. Earlier index-linked references, not independent passenger confirmation: EFTA02727229. |
| 2001-03-16 | PBI to MIA | Original log p. 81, trip 1474: date and route present. BK only; the initials do not establish identity. Filed schedule p. 25 also contains the dated route, with redacted passenger fields. Earlier index-linked references, not independent passenger confirmation: EFTA02796838; EFTA02727229. |
| 2001-03-16 | MIA to STT | Original log p. 81, trip 1475: date and route present. BK only; the initials do not establish identity. Filed schedule p. 25 also contains the dated route, with redacted passenger fields. Earlier index-linked references, not independent passenger confirmation: EFTA02796838; EFTA02727229. |
| 2001-03-19 | STT to LGA | EFTA02796838 (source listed by index); EFTA02727229 (source listed by index) |
| 2001-03-27 | PBI to TEB | EFTA02796838 (source listed by index); EFTA02727229 (source listed by index) |
| 2001-03-29 | TEB to SAF | EFTA02796838 (source listed by index); EFTA02727229 (source listed by index) |
| 2001-04-05 | TEB to PBI | Derivative transcription only; original row requires separate verification |
| 2001-04-09 | PBI to ACY | EFTA02796838 (source listed by index) |
| 2001-04-09 | ACY to TEB | EFTA02796838 (source listed by index) |
| 2001-04-11 | TEB to STT | EFTA02796838 (source listed by index) |
| 2001-04-16 | STT to PBI | EFTA02796838 (source listed by index) |
| 2001-04-17 | PBI to TEB | EFTA02796838 (source listed by index) |
| 2001-04-20 | TEB to PBI | EFTA02796838 (source listed by index) |
| 2001-04-27 | TEB to SAF | Derivative transcription only; original row requires separate verification |
| 2001-05-14 | STT to TEB | EFTA02796838 (source listed by index) |
| 2001-06-01 | TEB to PBI | EFTA02727230 (source listed by index) |
| 2001-06-03 | PBI to STT | EFTA02796838 (source listed by index); EFTA02727230 (source listed by index) |
| 2001-06-05 | STT to TEB | EFTA02796838 (source listed by index); EFTA02727230 (source listed by index) |
| 2001-08-24 | HPN to PBI | EFTA02796838 (source listed by index); EFTA02727232 (source listed by index) |
| 2001-08-27 | PBI to HPN | EFTA02796838 (source listed by index); EFTA02727232 (source listed by index) |
| 2001-08-29 | HPN to STT | EFTA02796838 (source listed by index); EFTA02727232 (source listed by index) |
| 2001-09-03 | STT to HPN | EFTA02796838 (source listed by index); EFTA02727232 (source listed by index) |
| 2001-09-06 | HPN to PBI | EFTA02796838 (source listed by index); EFTA02727232 (source listed by index) |
| 2001-09-09 | PBI to HPN | EFTA02796838 (source listed by index); EFTA02727232 (source listed by index) |
Banu Kucukkoylu in Separate Records
A December 2002 FedEx account record contains a sender name rendered Banu Kucukkoylu and a recipient named Edwina Simmonds. The shipment was dropped off December 18 and recorded as delivered December 19. The invoice documents a shipment, not the envelope’s contents, a meeting or an unlawful purpose.
Shoppers Travel transaction records also include the name Kucukkoylu/Banu, with further appearances on page 10. A travel agency invoice is evidence of a transaction in its accounting system. Its date is not necessarily a flight date, and an invoiced name does not establish that the named person boarded.
A 2016 civil litigation disclosure lists Banu Kucukkoylu as a person the litigant said had relevant knowledge. That description is a party’s disclosure statement. It is not a court finding, a criminal charge or proof that the listed person gave the proposed testimony.
The Court Rejected the Doe 102 Identification
Judge Loretta Preska’s January 15, 2024 order states that material submitted under seal persuaded the court that Banu Kucukkoylu was not Doe 102. The court also said false reporting about that identification had endangered her. The public order controls this point: the Doe 102 attribution must not be repeated as fact.
Teyit’s fact checking report separately discusses mistaken public identifications and the response of a Turkish namesake. Neither the name similarity nor a beauty pageant biography identifies the passenger in these records. This article therefore documents names appearing in records while leaving any disputed personal identification unresolved.
Questions and Unresolved Issues
- What is the reliable count of distinct 2001 legs after removing duplicate release copies?
- How is the passenger’s surname actually written in each original log?
- Does any primary document link the traveler to a verified professional or biographical identity?
- Which flight records preserve named or redacted fellow passengers and what privacy protections are needed?
- Do border and immigration records provide independent corroboration of the international legs?
Related EpsteinWiki Articles
- Flights and Travel Research Tools explains how original logs and derived schedules are verified.
- JFlights and JMail explains differences among indexes.
- Who Went to Zorro Ranch? shows how aviation records intersect with property histories without proving every visit.
Sources
- EFTA00218048 page 17
- DOJ-OGR-00015291
- EFTA01182998 page 56
- January 15, 2024 identity correction order, Giuffre v. Maxwell, filing 1340
- Teyit, reporting on mistaken identity claims
- Government Exhibit 662 RR, original flight log collection.
- Subject relevant indexed flight records, a finding aid to verify against the original.
- June 2001 indexed legs and August and September 2001 indexed legs.
- Epstein Data cross referenced aviation index.