WELL · 42-447-35728 · DISTRICT 7
JBM E #1
Throckmorton County · Throckmorton County Regular field · Vertical
Jbm E #1 (API 42-447-35728) is a plugged well in Throckmorton County, plugged September 22, 2000, last operated by Cottonwood Petroleum CO..
The RRC has issued one drilling permit, issued April 24, 1997, permitted to 1,000 ft.
Completion filings report one formation top, including Noodle Creek.
Its lease has reported 1.51K barrels of oil and 40 mcf of gas since June 1997, last reporting in November 2000.
Operator of record
- Based in
- Abilene, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Feb 4, 2009
- Permits on file
- 454
- Phone
- (325) 676-5557
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Cottonwood Petroleum Co. |
| Production reports | Cottonwood Petroleum Co.through Sep 2000 |
| Latest permit | Cottonwood Petroleum Co.Apr 24, 1997 |
- 1,000
- total depth, ft
- 1
- permits on file
- Apr 24, 1997
- last permit issued
- Jun 23, 1997
- completed
- 1.51K
- cumulative oil, bbl
- 40
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 1997 THROUGH Nov 2000
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 23, 1997
- Shut in
- —
- Plugged
- Sep 22, 2000
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 |
|---|---|---|---|---|---|---|
| JBM "E" O-8-28194 | Throckmorton County Regular | Cottonwood Petroleum Co. | 1 | 1.51K | 40 | Jun 1997 – Nov 2000 |
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.
- 1Cottonwood Petroleum Co.Jul 1997 → Aug 2000
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 461580-99 | Drill | Cottonwood Petroleum Co. | Apr 24, 1997 | Apr 24, 1997 | May 23, 1997 | 1,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-8-28194 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,247 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Noodle Creek | 480 | 767 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 680 | 687 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 790 | 6.75 | 150 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 29, 1997 | Jun 27, 1997 | Yes |
| 00 | Aug 5, 1997 | — | — |
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-447-35728 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-447-35728 → 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/44735728, documented in the API reference.