WELL · 42-067-30559 · DISTRICT 6
Caver #3
Cass County · Lake Texarkna (Travis Peak) field · Vertical
Caver #3 (API 42-067-30559) is a plugged well in Cass County, plugged December 19, 1991, last operated by Newton Corp. The.
The RRC has issued one drilling permit, issued July 16, 1987, permitted to 9,500 ft.
It was permitted by James, T. L. & Company, Inc. and has since transferred to Newton Corp. The on the wellbore schedule.
Completion filings report 5 formation tops, including Ozan, Base Massive Anhyd, Sligo, Buckner.
Operator of record
Permitted by James, T. L. & Company, Inc.; the EWA schedule now lists a different operator.
Dallas, TX · P-5 Y, filed Nov 5, 2021 · 1 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Newton Corp. The |
| Production reports | none |
| Latest permit | James, T. L. & Company, Inc.Jul 16, 1987 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 9,500
- total depth, ft
- 1
- permits on file
- Jul 16, 1987
- last permit issued
- Nov 4, 1987
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2008
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Nov 4, 1987
- Shut in
- —
- Plugged
- Dec 19, 1991
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 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Caver O-6-12258 | Lake Texarkna (Travis Peak) | Newton Corp.,the | 2 | 0 | 0 | Jan 1993 – Mar 2008 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 332646-99 | Drill | James, T. L. & Company, Inc. | Jul 9, 1987 | Jul 16, 1987 | Sep 30, 1987 | 9,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-6-12258 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 250 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,212 | 6,219 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 2,103 | 12.25 | 680 S |
| 5.5 | 6,300 | 8.75 | 565 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 | Feb 25, 1988 | Jan 22, 1988 | — |
| 00 | Jan 6, 1988 | Nov 12, 1987 | Yes |
| 00 | Dec 19, 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.
- Wellbore filings for 42-067-30559 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-067-30559 → 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/06730559, documented in the API reference.