WELL · 42-239-33642 · DISTRICT 2

Edmonia Pressly #18

Y

Jackson County · Cordele (M-2) field · Producing  · Vertical

Edmonia Pressly #18 (API 42-239-33642) is a well in Jackson County operated by Cordele Development Corporation, completed August 4, 2015 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 23, 2014, permitted to 3,000 ft.

Completion filings report 4 formation tops, including Miocene (undifferentiated), Catahoula, Gretta - Disposal, Frio.

Its lease has reported 53.4K barrels of oil since February 2010, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Cordele Development Corporation

San Antonio, TX · P-5 Y, filed Dec 4, 2025 · 63 permits on file · (210) 710-4917

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCordele Development Corporation
Production reportsCordele Development Corporationthrough Mar 2026
Latest permitCordele Development CorporationSep 23, 2014
3,000
total depth, ft
1
permits on file
Sep 23, 2014
last permit issued
Aug 4, 2015
completed
53.4K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Aug 4, 2015
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Edmonia Pressly O-2-9450Cordele (M-2)Cordele Development Corporation253.4K0Feb 2010 – Jul 2026

Oil, barrels lease total

Last 12 months 217 · prior 12 479(-55%)

050100150202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Cordele Development CorporationFeb 2010 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
794214-99DrillCordele Development CorporationAug 14, 2014Sep 23, 2014Oct 14, 20143,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-9450————

Formation tops

As filed on W-2/G-1. Subsea from 86 ft elevation.Download CSV →

FormationMD ftSubsea
Miocene (undifferentiated)MIOCENE (M-2) CORDELE A SAND2,550-2,464
Miocene (undifferentiated)MIOCENE (M-1) CORDELE B SAND2,637-2,551
Miocene (undifferentiated)MIOCENE (CORDELE D SAND)2,720-2,634
CatahoulaCATAHOULA - DISPOSAL, H2S (CORDE3,050-2,964
Gretta - Disposal3,500-3,414
FrioFRIO - DISPOSAL3,750-3,664

Perforations

Perforated and open-hole intervals.

FromToType
2,6372,643Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,46012.25665 S
5.52,8007.875300 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Apr 19, 2016Sep 23, 2015Yes

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/23933642, documented in the API reference.