WELL · 42-447-34538 · DISTRICT 7

Bailey Z #4

Plugged

Throckmorton County · Throckmorton County Regular field  · Vertical

Bailey Z #4 (API 42-447-34538) is a plugged well in Throckmorton County, plugged February 6, 1995, last operated by M. & K. Development CO..

The RRC has issued one drilling permit, issued December 30, 1985, permitted to 990 ft.

It was permitted by Sierra Special Oil Company and has since transferred to M. & K. Development CO. on the wellbore schedule.

Completion filings report one formation top, including Gunsight.

Its 2 leases have reported 308 barrels of oil and 50 mcf of gas since January 1993, last reporting in August 2003. The leases carry 10 wells, so these are lease totals, not this well alone.

Operator of record

M. & K. Development Co.

Permitted by Sierra Special Oil Company; the EWA schedule now lists a different operator.

Lolita, TX · P-5 Y, filed Mar 7, 1997 · 4 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleM. & K. Development Co.
Production reportsM. & K. Development Co.through Feb 1997
Latest permitSierra Special Oil CompanyDec 30, 1985

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

990
total depth, ft
1
permits on file
Dec 30, 1985
last permit issued
Jan 24, 1986
completed
308
cumulative oil, bbl
50
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Aug 2003

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 24, 1986
Shut in
—
Plugged
Feb 6, 1995

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 2 leases this well is completed on; they carry 10 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bailey Z O-8-23310Throckmorton County RegularM. & K. Development Co.630850Jan 1993 – Aug 2003
Bailey O-8-25775Throckmorton County RegularCreswell, Gene400Jan 1993 – Aug 2003

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. 1M. & K. Development Co.Jan 1993 → Sep 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
293755-99DrillSierra Special Oil CompanyDec 30, 1985Dec 30, 1985—990

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-23310————
—— O-8-25775————

Formation tops

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

FormationMD ftSubsea
Gunsight357848

Perforations

Perforated and open-hole intervals.

FromToType
359363Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.54306.75115 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
00May 4, 1990Feb 4, 1986Yes
00Apr 12, 1990——
00Feb 26, 1986Feb 4, 1986Yes
00Feb 14, 1986——

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