WELL · 42-025-33894 · DISTRICT 2

Hynes James Agnes #31

Y

Bee County · Papalote E. (3200 B Stringer) field · Shut IN  · Vertical

Hynes James Agnes #31 (API 42-025-33894) is a well in Bee County operated by Formation Resour Field Svcs LLC, completed March 25, 2014 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued September 16, 2013, permitted to 3,500 ft.

It was permitted by Spindletop Drilling CO. and has since transferred to Formation Resour Field Svcs LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Swd Zone, Catahoula.

Its lease has reported 2.32K barrels of oil since March 2014, last reporting in July 2026.

Operator of record

Formation Resour Field Svcs LLC

Permitted by Spindletop Drilling Co.; the EWA schedule now lists a different operator.

Woodward, OK · P-5 Y, filed Aug 4, 2025 · (806) 440-4844

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleFormation Resour Field Svcs LLC
Production reportsSpindletop Drilling Co.through Mar 2017
Latest permitSpindletop Drilling Co.Sep 16, 2013

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

3,500
total depth, ft
1
permits on file
Sep 16, 2013
last permit issued
Mar 25, 2014
completed
2.32K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2014 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 25, 2014
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Hynes, James Agnes O-2-11038Papalote, E. (3200 B Stringer)Formation Resour Field Svcs, LLC12.32K0Mar 2014 – Jul 2026

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. 1Spindletop Drilling Co.Apr 2014 → Mar 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
769059-99DrillSpindletop Drilling Co.Aug 27, 2013Sep 16, 2013Feb 19, 20143,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-2-11038————

Formation tops

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

FormationMD ftSubsea
SWD Zone2,318-2,240
CatahoulaCATAHOULA "A"3,058-2,980
CatahoulaCATAHOULA "B"3,080-3,002
CatahoulaCATAHOULA "C"3,099-3,021

Perforations

Perforated and open-hole intervals.

FromToType
3,2413,242Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62536712.25265 S
4.53,2677.875517 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
00Dec 10, 2015Jul 24, 2014Yes

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