WELL · 42-429-33265 · DISTRICT 7
Kennedy #2
Stephens County · Stephens County Regular (Gas) field · Vertical
Kennedy #2 (API 42-429-33265) is a plugged well in Stephens County, plugged April 22, 2026, last operated by Jeff Dooley Operating LLC.
The RRC has issued one drilling permit, issued April 22, 1982, permitted to 4,800 ft.
It was permitted by Wes-Mor Drilling, Inc. and has since transferred to Jeff Dooley Operating LLC on the wellbore schedule.
Operator of record
Permitted by Wes-Mor Drilling, Inc.; the EWA schedule now lists a different operator.
Breckenridge, TX · P-5 Y, filed Jan 5, 2026 · 2 permits on file · (254) 559-0990
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Jeff Dooley Operating LLC |
| Production reports | Jeff Dooley Operating, LLCthrough Feb 2026 |
| Latest permit | Wes-Mor Drilling, Inc.Apr 22, 1982 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 4,800
- total depth, ft
- 1
- permits on file
- Apr 22, 1982
- last permit issued
- Jun 8, 1982
- completed
- 0
- cumulative oil, bbl
- 626K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Jun 8, 1982
- Shut in
- —
- Plugged
- Apr 22, 2026
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 |
|---|---|---|---|---|---|---|
| Kennedy G-8-99947 | Stephens County Regular (Gas) | Jeff Dooley Operating, LLC | 1 | 0 | 626K | Jan 1993 – Apr 2026 |
Gas, mcf lease total
Last 12 months 1,632 · prior 12 12,429(-87%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Wes-Mor Drilling, Inc.Jan 1993 → Mar 1993
- 2McKee, Kenneth W. Oil Co.Apr 1993 → May 2011
- 3Dooley, JeffJun 2011 → Apr 2012
- 4Jeff Dooley Operating, LLCMay 2012 → Feb 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 157693-99 | Drill | Wes-Mor Drilling, Inc. | Apr 22, 1982 | Apr 22, 1982 | — | 4,800 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-99947 | — | — | — | — |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 212 | 12.25 | 130 S |
| 2.375 | 3,946 | — | — |
| 4.5 | 4,207 | 7.875 | 275 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 | Jan 12, 1984 | Jun 16, 1982 | — |
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-429-33265 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-429-33265 → 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/42933265, documented in the API reference.