TEXAS · WELLS · LOVING COUNTY · LUDEMAN 22 LEASE · API 42-301-31229 · DISTRICT 7B
Ludeman 22 #1
Loving County · Haley (Lwr. Wolfcamp-Penn Cons.) field · Producing · Vertical
Ludeman 22 #1 (API 42-301-31229) is a well in Loving County operated by Anadarko E&P Onshore LLC, completed November 12, 2005 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued April 14, 2005, permitted to 17,514 ft.
It was permitted by Anadarko Petroleum Corporation and has since transferred to Anadarko E&P Onshore LLC on the wellbore schedule.
Completion filings report 4 formation tops, including Bell Canyon, Cherry Canyon, Wolfcamp, Strawn.
Its lease has reported 16.6K barrels of oil and 2.82M mcf of gas since November 2005, last reporting volume in April 2026.
Operator of record
Permitted by Anadarko Petroleum Corporation; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active (A)
- P-5 last filed
- Oct 22, 2025
- Permits on file
- 4,576
- Phone
- (713) 215-7000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Anadarko E&P Onshore LLC |
| Production reports | Anadarko E&P Onshore LLCthrough Apr 2026 |
| Latest permit | Anadarko Petroleum CorporationApr 14, 2005 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 17,514
- total depth, ft
- 1
- permits on file
- Apr 14, 2005
- last permit issued
- Nov 12, 2005
- completed
- 16.6K
- cumulative oil, bbl
- 2.82M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Nov 2005 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Nov 12, 2005
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active – Extension (X)
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 |
|---|---|---|---|---|---|---|
| Ludeman 22 G-10-215284 | Haley (Lwr. Wolfcamp-Penn Cons.) | Anadarko E&P Onshore LLC | 1 | 16.6K | 2.82M | Nov 2005 – Apr 2026 |
Gas, mcf lease total
Last 12 months 85,585 · prior 12 103,324(-17%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Anadarko Petroleum CorporationNov 2005 → Mar 2013
- 2Anadarko E&P Onshore LLCApr 2013 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 560393-99 | Drill | Anadarko Petroleum Corporation | Apr 13, 2005 | Apr 14, 2005 | Jun 14, 2005 | 18,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Nov 12, 2005 | Ludeman 22 G-10-215284 | Haley (Lwr. Wolfcamp-Penn Cons.) | Anadarko E&P Onshore LLC | Producing | 17,514 |
Formation tops
As filed on W-2/G-1. Subsea from 3,120 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Bell Canyon | 5,299 | -2,179 |
| Cherry Canyon | 6,325 | -3,205 |
| Wolfcamp | 12,280 | -9,160 |
| Strawn | 14,476 | -11,356 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 14,874 | 17,204 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 5,346 | 17.5 | 4,250 S |
| 9.625 | 13,200 | 12.25 | 1,050 S |
| 5.5 | 17,512 | 8.75 | 1,625 S |
| 9.625 | — | 12.25 | 1,400 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 | Aug 14, 2006 | Apr 5, 2006 | Yes |
| 00 | Apr 14, 2006 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Oct 17, 2008. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITYSpans Bell Canyon, Cherry Canyon, Wolfcamp, Strawn | TIFF | 5,337 to 17,511 | Oct 17, 2008run Sep 21, 2005 | 6.07 |
"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.
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-301-31229 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-301-31229 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/30131229, documented in the API reference.