WELL · 42-001-32545 · DISTRICT 6
Bentley #1
Anderson County · Cayuga (CV-TP Cons.) field · Producing · Vertical
Bentley #1 (API 42-001-32545) is a well in Anderson County operated by O Ryan Oil And Gas, completed June 26, 2007 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued February 2, 2007, permitted to 11,300 ft.
Completion filings report 3 formation tops, including Rodessa, Pettit, Cv-Tp Cons..
No lease production has been reported under this well’s leases.
Operator of record
- Based in
- Odessa, TX
- P-5 status
- Active – Hearing (H)
- P-5 last filed
- Feb 24, 2026
- Permits on file
- 96
- Phone
- (432) 550-2112
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | O Ryan Oil and Gas |
| Production reports | O'Ryan Oil and Gasthrough Apr 2026 |
| Latest permit | O'Ryan Oil and GasFeb 2, 2007 |
- 11,300
- total depth, ft
- 1
- permits on file
- Feb 2, 2007
- last permit issued
- Jun 26, 2007
- completed
- 0
- cumulative oil, bbl
- 757K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2007 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jun 26, 2007
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active – Hearing (H)
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Bentley G-6-227741 | Cayuga (CV-TP Cons.) | O'Ryan Oil and Gas | 1 | 0 | 757K | Apr 2007 – Jul 2026 |
Gas, mcf lease total
Last 12 months 11,792 · prior 12 14,077(-16%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1O'Ryan Oil and GasJul 2007 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 631997-99 | Drill | O'Ryan Oil and Gas | Jan 16, 2007 | Feb 2, 2007 | Feb 19, 2007 | 11,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-6-227741 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 265 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 10,965 | 11,095 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 2,213 | 12.25 | 1,050 S |
| 5.5 | 11,175 | 7.875 | 1,100 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Sep 5, 2007 | May 10, 2007 | — |
| 00 | Aug 31, 2007 | Jul 25, 2007 | Yes |
| 00 | Jul 9, 2007 | — | — |
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.
- Wellbore filings for 42-001-32545 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-001-32545 → scanned completion filings
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/00132545, documented in the API reference.