WELL · 42-371-34748 · DISTRICT 8

I. R. T. -B- #4

Y

Pecos County · Lehn-Apco (1600) field · Producing  · Vertical

I. R. T. -B- #4 (API 42-371-34748) is a well in Pecos County operated by Porosity Oil LLC, completed April 20, 1984 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 10, 1984, permitted to 2,000 ft.

It was permitted by D G D Oil CO. and has since transferred to Porosity Oil LLC on the wellbore schedule.

Completion filings report one formation top, including Queens.

Its lease has reported 28.7K barrels of oil and 149 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

Porosity Oil LLC

Permitted by D G D Oil Co.; the EWA schedule now lists a different operator.

Imperial, TX · P-5 Y, filed Aug 4, 2025 · (432) 208-8402

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePorosity Oil LLC
Production reportsPorosity Oil LLCthrough Apr 2026
Latest permitD G D Oil Co.Feb 10, 1984

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
Feb 10, 1984
last permit issued
Apr 20, 1984
completed
28.7K
cumulative oil, bbl
149
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 20, 1984
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 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
I. R. T. -B- O-10-3497Lehn-Apco (1600)Porosity Oil LLC328.7K149Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 779 · prior 12 1,033(-25%)

050100150202420252026

Chain of custody

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

  1. 1D G D Oil Co.Jan 1993 → Jun 2000
  2. 2Graham, H.E.Jul 2000 → Mar 2007
  3. 3Bugington Energy, LLCApr 2007 → Oct 2015
  4. 4Porosity Oil LLCNov 2015 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
229123-99DrillD G D Oil Co.Feb 8, 1984Feb 10, 1984Mar 12, 19842,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-3497————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Queens1,614

Perforations

Perforated and open-hole intervals.

FromToType
1,6141,730Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62560511225 S
5.52,0007.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
00Jun 20, 1984May 17, 1984—
00Jun 6, 1984May 17, 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/37134748, documented in the API reference.