WELL · 42-371-33536 · DISTRICT 8

White & Baker -D- #3

Y

Pecos County · White & Baker field · Producing  · Vertical

White & Baker -D- #3 (API 42-371-33536) is a well in Pecos County operated by M.A.R.S. Energy, completed December 23, 1981 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued August 7, 1981, permitted to 2,000 ft.

It was permitted by Dbh Petroleum, Inc. and has since transferred to M.A.R.S. Energy on the wellbore schedule.

Its lease has reported 13.2K barrels of oil and 21.5K mcf of gas since January 1993, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

M.A.R.S. Energy

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

Midland, TX · P-5 Y, filed Mar 4, 2026 · 5 permits on file · (325) 428-7988

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleM.A.R.S. Energy
Production reportsM.A.R.S. Energythrough Mar 2026
Latest permitDBH Petroleum, Inc.Aug 7, 1981

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

2,000
total depth, ft
1
permits on file
Aug 7, 1981
last permit issued
Dec 23, 1981
completed
13.2K
cumulative oil, bbl
21.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 23, 1981
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
White & Baker -D- O-10-26566White & BakerM.A.R.S. Energy313.2K21.5KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 1,136 · prior 12 1,473(-23%)

0200400202420252026

Chain of custody

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

  1. 1B & H Oilfield ServicesJan 1993 → Jul 1996
  2. 2Dixon, N. D.Aug 1996 → Oct 2000
  3. 3Green Bay Oil & GasNov 2000 → Aug 2004
  4. 4Pharaoh Oil & Gas, Inc.Sep 2008 → Mar 2013
  5. 5Julana Oil & GasMay 2013 → Sep 2013
  6. 6MKS ResourcesOct 2013 → Mar 2021
  7. 7M.A.R.S. EnergyAug 2023 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
129101-99DrillDBH Petroleum, Inc.Aug 7, 1981Aug 7, 1981—2,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-26566————

Perforations

Perforated and open-hole intervals.

FromToType
1,8401,908Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62559011300 S
2.3751,875——
4.51,9007.875250 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, 1984Jan 13, 1982—

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