TEXAS · WELLS · FAYETTE COUNTY · API 42-149-32635 · DISTRICT 03
Kunze-Kasper Unit #1
Fayette County · Giddings (North Edwards) field · Horizontal
Kunze-Kasper Unit #1 (API 42-149-32635) is a plugged horizontal well in Fayette County, plugged April 4, 2003, last operated by Anadarko E&P Company LP.
The RRC has issued 3 drilling permits between 1992 and 1996, permitted to 13,800 ft.
It was permitted by Union Pacific Resources Company and has since transferred to Anadarko E&P Company LP on the wellbore schedule.
Completion filings report 9 formation tops, including Midway, Navarro, Taylor, Pecan Gap.
Its 2 leases have reported 62.1K barrels of oil and 4.35M mcf of gas since January 1993, with no volume in the three years through April 2026. The leases carry 2 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Union Pacific Resources Company; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Sep 27, 2012
- Permits on file
- 2,635
- Phone
- (832) 636-3130
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Anadarko E&P Company LP |
| Production reports | Anadarko E&P Company LPthrough Jan 2003 |
| Latest permit | Union Pacific Resources CompanyNov 25, 1996 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 13,800
- total depth, ft
- 3
- permits on file
- Nov 25, 1996
- last permit issued
- May 16, 1996
- completed
- 62.1K
- cumulative oil, bbl
- 4.35M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 2003
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 16, 1996
- Shut in
- —
- Plugged
- Apr 4, 2003
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 2 leases 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 |
|---|---|---|---|---|---|---|
| Kunze-Kasper Unit G-3-160757 | Giddings (North Edwards) | Anadarko E&P Company LP | 1 | 60K | 4.34M | May 1996 – Jan 2003 |
| Kunze-Kasper Unit O-3-21671 | Giddings (Austin Chalk-3) | Union Pacific Resources Company | 1 | 2.1K | 1.8K | Jan 1993 – Jul 1993 |
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.
- 1Union Pacific Resources CompanyJan 1993 → Jan 2001
- 2Rme Petroleum CompanyFeb 2001 → Sep 2002
- 3Anadarko E&P Company LPDec 2002 → Jan 2003
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 455447-99 | Recompletion | Union Pacific Resources Company | Nov 20, 1996 | Nov 25, 1996 | Apr 17, 1996 | 13,270 |
| 414098-99 | Recompletion | Union Pacific Resources Company | Jul 21, 1993 | Jul 21, 1993 | Jul 31, 1993 | 13,000 |
| 399750-99 | Drill | Union Pacific Resources Company | May 28, 1992 | May 29, 1992 | Jul 1, 1992 | 13,800 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| May 16, 1996 | Kunze-Kasper Unit G-3-160757 | Giddings (North Edwards) | Anadarko E&P Company LP | Plugged | — |
| Sep 23, 1993 | Kunze-Kasper Unit O-3-21671 | Giddings (Austin Chalk-3) | Union Pacific Resources Company | Plugged | — |
| Sep 23, 1993 | Kunze-Kasper Unit O-3-21671 | Giddings (Austin Chalk-3) | Union Pacific Resources Company | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 372 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Midway | 5,693 | -5,321 |
| Navarro | 6,506 | -6,134 |
| Taylor | 7,120 | -6,748 |
| Pecan Gap | 7,894 | -7,522 |
| Austin Chalk | 8,384 | -8,012 |
| Austin Chalk | 8,389 | -8,017 |
| Eagle FordEAGLEFORD | 9,152 | -8,780 |
| Buda | 9,198 | -8,826 |
| Edwards | 9,532 | -9,160 |
| Glen Rose | 10,010 | -9,638 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,504 | 13,270 | Perforated |
| 9,989 | 9,993 | Perforated |
| 10,006 | 10,012 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 10.75 | 2,004 | 14.75 | 745 S |
| 7.625 | 8,504 | 9.875 | 1,145 S |
| 2.875 | 10,077 | 6.75 | 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Dec 30, 1996 | Jun 27, 1996 | Yes |
| 00 | Dec 10, 1996 | — | — |
| 00 | Jan 14, 1994 | Dec 2, 1993 | Yes |
| 00 | Oct 13, 1992 | Aug 25, 1992 | Yes |
| 00 | Oct 8, 1992 | — | — |
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-149-32635 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-149-32635 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
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/14932635, documented in the API reference.