WELL · 42-383-31524 · DISTRICT 7

Pettit -A- #5

Plugged

Reagan County · Spraberry (Trend Area) field  · Vertical

Pettit -A- #5 (API 42-383-31524) is a plugged well in Reagan County, plugged May 4, 2006, last operated by De Central Operating LLC.

The RRC has issued one drilling permit, issued December 19, 1979, permitted to 7,800 ft.

It was permitted by Coquina Oil Corporation and has since transferred to De Central Operating LLC on the wellbore schedule.

Its lease has reported 38.1K barrels of oil and 344K mcf of gas since January 1993, last reporting in May 2026. The lease carries 5 wells, so these are lease totals, not this well alone.

Operator of record

DE Central Operating LLC

Permitted by Coquina Oil Corporation; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Nov 4, 2025 · 401 permits on file · (254) 559-7845

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDE Central Operating LLC
Production reportsDE IV Operating, LLCthrough Feb 2025
Latest permitCoquina Oil CorporationDec 19, 1979

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

7,800
total depth, ft
1
permits on file
Dec 19, 1979
last permit issued
Aug 23, 1980
completed
38.1K
cumulative oil, bbl
344K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 23, 1980
Shut in
—
Plugged
May 4, 2006

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Pettit -A- O-9-2998Spraberry (Trend Area)DE Central Operating, LLC538.1K344KJan 1993 – May 2026

Oil, barrels lease total

Last 12 months 0 · prior 12 355(-100%)

050100150202420252026

Gas, mcf lease total

Last 12 months 0 · prior 12 404(-100%)

0100200300202420252026

Chain of custody

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

  1. 1Enron Oil & Gas CompanyJan 1993 → Aug 1993
  2. 2Stephens, Autry C.Sep 1993 → Aug 2000
  3. 3Endeavor Energy Resources L.P.Sep 2000 → Oct 2023
  4. 4DE IV Operating, LLCNov 2023 → Feb 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
67274-99DrillCoquina Oil CorporationDec 19, 1979Dec 19, 1979Feb 23, 19807,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-2998————

Perforations

Perforated and open-hole intervals.

FromToType
6,7927,494Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62549111350 S
2.3756,798——
4.57,6577.875900 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
00Jan 12, 1984Aug 26, 1980—

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/38331524, documented in the API reference.