WELL · 42-219-30330 · DISTRICT 8
Levelland Unit #450
Hockley County · Vertical
Levelland Unit #450 (API 42-219-30330) is a permitted well in Hockley County filed by Occidental Permian Ltd.; no completion report is on file yet.
The RRC has issued one drilling permit, issued December 6, 2017, permitted to 4,600 ft.
Its lease has reported 90.1M barrels of oil and 53.9M mcf of gas since January 1993, last reporting in July 2026. The lease carries 1,212 wells, so these are lease totals, not this well alone.
Operator of record
Houston, TX · P-5 Y, filed Dec 4, 2025 · 6,251 permits on file · (713) 215-7000
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Occidental Permian Ltd.through Apr 2026 |
| Latest permit | Occidental Permian Ltd.Dec 6, 2017 |
- 4,600
- total depth, ft
- 1
- permits on file
- Dec 6, 2017
- last permit issued
- —
- completed
- 90.1M
- cumulative oil, bbl
- 53.9M
- 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
33.613203, -102.434486
OpenStreetMap → · Google Maps →
Permit surface location from the RRC GIS record, in Hockley County.
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; they carry 1,212 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Levelland Unit O-11-3780 | Levelland | Occidental Permian EOR, LLC | 1,212 | 90.1M | 53.9M | Jan 1993 – Jul 2026 |
Oil, barrels lease total
Last 12 months 1,056,098 · prior 12 1,181,912(-11%)
Gas, mcf lease total
Last 12 months 824,171 · prior 12 981,829(-16%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Amoco Production CompanyJan 1993 → Feb 1997
- 2Altura Energy Ltd.Mar 1997 → Apr 2000
- 3Occidental Permian Ltd.May 2000 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 833691-99 | Recompletion | Occidental Permian Ltd. | Nov 30, 2017 | Dec 6, 2017 | — | 4,600 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-11-3780 | — | — | — | — |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 451 | 12.25 | 275 S |
| 5.5 | 4,744 | 7.875 | 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 | Jan 12, 1984 | Jun 18, 1970 | — |
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-219-30330 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-219-30330 → 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.
Nearby wells and their tops
NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM
Draw a cross-section
This well has no tops filed, so it cannot anchor a section; its neighbours can.
Levelland Unit42-219-37420
2.8 KM · Occidental Permian Ltd. · Section with this well →
| Santa Rosa | 1,100 | 2,442 |
| Yates | 2,563 | 979 |
| Yates | 2,563 | 979 |
| San Andres | 4,443 | -901 |
| San Andres | 4,443 | -901 |
| Cisco | — | |
| Clear Fork | — | |
| Abo | — |
12 TOPS · FIRST 8
Levelland Unit42-219-37443
3.3 KM · Occidental Permian Ltd. · Section with this well →
| Santa Rosa | 315 | 3,232 |
| Yates | 2,640 | 907 |
| Cisco | — | |
| Wolfcamp | — | |
| Wichita-Albany | — | |
| Strawn | — | |
| San Andres | — | |
| Abo | — |
10 TOPS · FIRST 8
Levelland Unit42-219-30249
3.3 KM · Occidental Permian Ltd. · Section with this well →
| Rustler | 2,101 | 1,447 |
| Yates | 2,646 | 902 |
| San Andres | 4,728 | -1,180 |
North Levelland Unit42-219-37092
4.6 KM · Sabinal Energy Operating, LLC · Section with this well →
| Rustler | 2,086 | 1,496 |
| Yates | 2,595 | 987 |
| Grayburg | 3,591 | -9 |
| San Andres | 3,799 | -217 |
North Levelland Unit42-219-37501
4.6 KM · Sabinal Energy Operating, LLC · Section with this well →
| Santa Rosa | 972 | 2,618 |
| Yates | 2,602 | 988 |
| San Andres | 3,805 | -215 |
| Canyon | — | |
| Abo | — | |
| Cisco | — | |
| Clear Fork | — | |
| Strawn | — |
10 TOPS · FIRST 8
Inca42-219-37444
4.9 KM · Occidental Permian Ltd. · Section with this well →
| Santa Rosa | 2,078 | 1,450 |
| Yates | 2,629 | 899 |
| San Andres | 3,766 | -238 |
| Clear Fork | 5,856 | -2,328 |
| Wichita-Albany | 7,158 | -3,630 |
| Strawn | — | |
| Wolfcamp | — | |
| Abo | — |
10 TOPS · FIRST 8
Levelland Unit42-219-37472
5.4 KM · Occidental Permian Ltd. · Section with this well →
| Santa Rosa | 320 | 3,203 |
| Yates | 2,585 | 938 |
| San Andres | 3,790 | -267 |
| Abo | — | |
| Cisco | — | |
| Clear Fork | — | |
| Strawn | — | |
| Wichita-Albany | — |
10 TOPS · FIRST 8
Central Levelland Unit42-219-37452
7.3 KM · Occidental Permian Ltd. · Section with this well →
| Santa Rosa | 200 | 3,405 |
| Yates | 2,683 | 922 |
| San Andres | 4,872 | -1,267 |
| Wichita-Albany | — | |
| Strawn | — | |
| Abo | — | |
| Clear Fork | — | |
| Cisco | — |
10 TOPS · FIRST 8
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/21930330, documented in the API reference.