WELL · 42-237-40447 · DISTRICT 9
Sames #6
Jack County · Bryson East field · Producing · Vertical
Sames #6 (API 42-237-40447) is a well in Jack County operated by Covenant Operating LLC, completed October 12, 2016 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued September 16, 2016, permitted to 4,000 ft.
Completion filings report 10 formation tops, including Strawn, Bryson, Atoka, Butram.
Its lease has reported 47.2K barrels of oil since December 2013, last reporting in July 2026. The lease carries 5 wells, so these are lease totals, not this well alone.
Operator of record
Wichita Falls, TX · P-5 Y, filed Jan 4, 2026 · 85 permits on file · (940) 733-3018
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Covenant Operating LLC |
| Production reports | Covenant Operating, LLCthrough Apr 2026 |
| Latest permit | Covenant Operating, LLCSep 16, 2016 |
- 4,000
- total depth, ft
- 1
- permits on file
- Sep 16, 2016
- last permit issued
- Oct 12, 2016
- completed
- 47.2K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Dec 2013 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Oct 12, 2016
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active
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 5 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Sames O-13-32842 | Bryson, East | Covenant Operating, LLC | 5 | 47.2K | 0 | Dec 2013 – Jul 2026 |
Oil, barrels lease total
Last 12 months 844 · prior 12 1,122(-25%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Covenant Operating, LLCDec 2013 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 818477-99 | Drill | Covenant Operating, LLC | Sep 14, 2016 | Sep 16, 2016 | Sep 19, 2016 | 4,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-32842 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,234 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,458 | 2,460 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 556 | 12.25 | 300 S |
| 4.5 | 3,290 | 9.625 | 440 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 | Nov 18, 2016 | Nov 4, 2016 | Yes |
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-237-40447 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-237-40447 → 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/23740447, documented in the API reference.