WELL · 42-427-34515 · DISTRICT 4

Roos Bennett B #1

Y

Starr County · Boyle (H-) field · Producing  · Vertical

Roos Bennett B #1 (API 42-427-34515) is a well in Starr County operated by Hydrocarbon Operating Inc., completed July 28, 2010 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued June 14, 2010, permitted to 4,500 ft.

It was permitted by H & P Exploration CO. and has since transferred to Hydrocarbon Operating Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Frio, Vicksburg.

No lease production has been reported under this well’s leases.

Operator of record

Hydrocarbon Operating Inc.

Permitted by H & P Exploration Co.; the EWA schedule now lists a different operator.

Corpus Christ, TX · P-5 Y, filed Apr 4, 2026 · 32 permits on file · (361) 877-7557

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHydrocarbon Operating Inc.
Production reportsHydrocarbon Operating, Inc.through Sep 2025
Latest permitH & P Exploration Co.Jun 14, 2010

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

4,500
total depth, ft
2
permits on file
Jun 14, 2010
last permit issued
Jul 28, 2010
completed
0
cumulative oil, bbl
319K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 28, 2010
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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Roos Bennett B G-4-257356Boyle (H-)Hydrocarbon Operating, Inc.10319KJul 2010 – Jul 2026

Gas, mcf lease total

Last 12 months 23,374 · prior 12 33,991(-31%)

05K10K202420252026

Chain of custody

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

  1. 1H & P Exploration Co.Aug 2010 → Jul 2017
  2. 2Hydrocarbon Operating, Inc.Aug 2017 → Sep 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
697164-98DrillH & P Exploration Co.Aug 20, 2010Jun 14, 2010Jul 15, 20104,100
697164-99DrillH & P Exploration Co.Jun 7, 2010Jun 14, 2010—4,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-257356————

Formation tops

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

FormationMD ftSubsea
Frio1,850-1,586
Vicksburg3,950-3,686

Perforations

Perforated and open-hole intervals.

FromToType
3,7443,747Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62540512.25292 S
4.54,0987.875650 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
00Sep 29, 2010Sep 13, 2010Yes
00Sep 17, 2010——

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