WELL · 42-003-34027 · DISTRICT 8

Coffman #5

Plugged

Andrews County · Deep Rock (Devonian) field  · Vertical

Coffman #5 (API 42-003-34027) is a plugged well in Andrews County, plugged December 1, 2001, last operated by Maralo LLC.

The RRC has issued one drilling permit, issued February 23, 1984, permitted to 10,207 ft.

It was permitted by Maralo, Inc. and has since transferred to Maralo LLC on the wellbore schedule.

Completion filings report 6 formation tops, including Rustler, Yates, San Andres, Wolfcamp.

Its lease has reported 24.3K barrels of oil and 30.5K mcf of gas since January 1993, last reporting in February 2002. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Maralo LLC

Permitted by Maralo, Inc.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Sep 9, 2005 · 23 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMaralo LLC
Production reportsMaralo, LLCthrough Apr 2001
Latest permitMaralo, Inc.Feb 23, 1984

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

10,207
total depth, ft
1
permits on file
Feb 23, 1984
last permit issued
May 11, 1984
completed
24.3K
cumulative oil, bbl
30.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Feb 2002

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 11, 1984
Shut in
—
Plugged
Dec 1, 2001

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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Coffman O-10-27018Deep Rock (Devonian)Maralo, LLC324.3K30.5KJan 1993 – Feb 2002

No volumes reported on these leases in the last three years.

Chain of custody

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

  1. 1Maralo, Inc.Jan 1993 → Dec 1998
  2. 2Maralo, LLCJan 1999 → Apr 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
230316-99DrillMaralo, Inc.May 24, 1984Feb 23, 1984Mar 10, 198410,207

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-27018————

Formation tops

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

FormationMD ftSubsea
Rustler1,6751,510
Yates2,788397
San Andres4,255-1,070
WolfcampWOLFCAMP PAY8,498-5,313
PennsylvanianPENN LS MARKER8,739-5,554
Devonian10,076-6,891

Perforations

Perforated and open-hole intervals.

FromToType
10,07910,146Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37531517.5325 sx
8.6255,794112,000 sx
5.510,20713—

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
00Jul 9, 1984May 23, 1984—
00Jun 30, 1984May 23, 1984—

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) and the University Lands library. 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/00334027, documented in the API reference.