WELL · 42-365-00047 · DISTRICT 6
Rudman & Genecov #2A
Panola County · Vertical
Rudman & Genecov #2A (API 42-365-00047) is a permitted well in Panola County filed by Chevron U. S. A. Inc.; no completion report is on file yet.
The RRC has issued one drilling permit, issued January 11, 2006, permitted to 6,600 ft.
Operator of record
- Based in
- Midland, TX
- P-5 status
- Active (A)
- P-5 last filed
- Jan 30, 2026
- Permits on file
- 9,293
- Phone
- (866) 212-1212
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Pedernales Petroleum OP, LLCthrough Apr 2026 |
| Latest permit | Chevron U. S. A. Inc.Jan 11, 2006 |
- 6,600
- total depth, ft
- 1
- permits on file
- Jan 11, 2006
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 391K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 |
|---|---|---|---|---|---|---|
| Rudman & Genecov G-6-16072 | Hallsville, South (Page) | Pedernales Petroleum OP, LLC | 1 | 0 | 391K | Jan 1993 – Jul 2026 |
Gas, mcf lease total
Last 12 months 1,363 · prior 12 884(+54%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Roosth & Genecov Production Co.Jun 1995 → Apr 1997
- 2Roosth Production Co.May 1997 → Dec 1997
- 3Fair Oil, LCJan 1998 → Nov 1999
- 4Fair Oil, Ltd.Dec 1999 → Oct 2000
- 5Brisita Energy CorporationNov 2000 → May 2004
- 6Rippy Oil CompanyJun 2004 → May 2005
- 7Chevron U. S. A. Inc.Jun 2005 → Jun 2007
- 8Bachtell Oil & Gas, Ltd.Jul 2008 → May 2013
- 9Basa Resources, Inc.Jun 2013 → Nov 2016
- 10Pedernales Petroleum OP, LLCDec 2016 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 611909-99 | Recompletion | Chevron U. S. A. Inc. | Jan 5, 2006 | Jan 11, 2006 | — | 6,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-6-16072 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,567 | 6,579 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 658 | — | — |
| 2.375 | 6,563 | — | — |
| 5.5 | 6,634 | — | — |
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 | Oct 4, 1955 | — |
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-365-00047 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-365-00047 → 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/36500047, documented in the API reference.