WELL · 42-227-34145 · DISTRICT 8

Otis, John -B- #5

N

Howard County  · Vertical

Otis, John -B- #5 (API 42-227-34145) is a permitted well in Howard County filed by Legacy Reserves Operating LP; no completion report is on file yet.

The RRC has issued 2 drilling permits between 1987 and 2011, permitted to 4,000 ft.

Completion filings report 2 formation tops, including San Andres, Clear Fork.

Its 2 leases have reported 22.4K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2026. The leases carry 6 wells, so these are lease totals, not this well alone.

Operator of record

Legacy Reserves Operating LP

Denver, CO · P-5 Y, filed Oct 4, 2025 · 439 permits on file · (720) 498-3026

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsExtex Operating Companythrough Apr 2026
Latest permitLegacy Reserves Operating LPOct 17, 2011
4,000
total depth, ft
2
permits on file
Oct 17, 2011
last permit issued
—
completed
22.4K
cumulative oil, bbl
21
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
John Otis -B- O-10-41844Howard Glasscock (Consolidated)Extex Operating Company510.9K0Dec 2011 – Jul 2026
Otis, John -B- O-10-31131Howard Glasscock (Clear Fork,mi)Legacy Reserves Operating LP111.5K21Jan 1993 – Nov 2012

Oil, barrels lease total

Last 12 months 563 · prior 12 704(-20%)

0100200202420252026

Chain of custody

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

  1. 1Guthrie, A. K. Operating Co.Jan 1993 → Mar 1996
  2. 2Marathon Oil CompanyApr 1996 → Jul 1998
  3. 3Brothers Production Company Inc.Nov 1999 → Mar 2006
  4. 4Legacy Reserves Operating LPApr 2006 → Jan 2021
  5. 5Extex Operating CompanyFeb 2021 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
726034-99RecompletionLegacy Reserves Operating LPOct 11, 2011Oct 17, 2011—3,820
326293-99DrillGuthrie, A. K. Operating Co.Feb 9, 1987Feb 11, 1987—4,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-31131————
—— O-10-41844————

Formation tops

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

FormationMD ftSubsea
San Andres1,940513
Clear ForkCLEARFORK3,298-845

Perforations

Perforated and open-hole intervals.

FromToType
3,2873,634Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62518312.25150 S
5.53,8207.875600 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
00Oct 15, 2012Mar 19, 1987Yes
00Apr 6, 1987Mar 19, 1987Yes
00Mar 25, 1987——

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