TEXAS · WELLS · HOCKLEY COUNTY · NORTHEAST LEVELLAND UNIT LEASE · API 42-219-33404 · DISTRICT 7B
Northeast Levelland Unit #24
Hockley County · Levelland field · Injection · Vertical
Northeast Levelland Unit #24 (API 42-219-33404) is a well in Hockley County operated by Hilcorp Energy Company, completed January 2, 2024 and listed as injection on the RRC schedule.
The RRC has issued 2 drilling permits between 1981 and 2008, permitted to 4,930 ft.
It was permitted by Occidental Permian Ltd. and has since transferred to Hilcorp Energy Company on the wellbore schedule.
Completion filings report one formation top, including San Andres.
Its lease has reported 3.57M barrels of oil and 991K mcf of gas since January 1993, last reporting volume in April 2026. The lease carries 37 wells, so these are lease totals, not this well alone.
It holds an active disposal or injection permit, with 56.7K barrels injected in the 12 months reported through February 2026.
Operator of record
Permitted by Occidental Permian Ltd.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Mar 27, 2026
- Permits on file
- 3,458
- Phone
- (713) 209-2400
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Hilcorp Energy Company |
| Production reports | Hilcorp Energy Companythrough Apr 2026 |
| Latest permit | Occidental Permian Ltd.Nov 17, 2008 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 4,930
- total depth, ft
- 2
- permits on file
- Nov 17, 2008
- last permit issued
- Jan 2, 2024
- completed
- 3.57M
- cumulative oil, bbl
- 991K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jan 2, 2024
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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; they carry 37 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Northeast Levelland Unit O-11-61137 | Levelland | Hilcorp Energy Company | 37 | 3.57M | 991K | Jan 1993 – Apr 2026 |
Oil, barrels lease total
Last 12 months 39,636 · prior 12 24,772(+60%)
Gas, mcf lease total
Last 12 months 14,880 · prior 12 23,540(-37%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Shell Western E&P Inc.Jan 1993 → Nov 1994
- 2Shell Land & Energy Co.Dec 1994 → Feb 1997
- 3Altura Energy Ltd.Mar 1997 → Apr 2000
- 4Occidental Permian Ltd.May 2000 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 674796-99 | Reenter | Occidental Permian Ltd. | Nov 11, 2008 | Nov 17, 2008 | Aug 6, 2008 | 5,200 |
| 144990-99 | Drill | Sun Expl. & Prod. Co.-Midland | Dec 21, 1981 | Dec 21, 1981 | Mar 4, 1982 | 5,100 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jan 2, 2024 | Northeast Levelland Unit O-11-61137 | Levelland | Hilcorp Energy Company | Injection | 4,930 |
| Mar 27, 1982 | Northeast Levelland Unit O-11-61137 | Levelland | Hilcorp Energy Company | Plugged | — |
Formation tops
As filed on W-2/G-1. Subsea from 3,522 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| San Andres | 3,876 | -354 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 4,816 | 4,878 | Perforated |
| 4,830 | 4,890 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 485 | 12.25 | 350 S |
| 2.375 | 4,699 | — | — |
| 5.5 | 4,927 | 7.875 | 1,800 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 | Nov 1, 2024 | Apr 12, 2024 | — |
| 00 | Aug 12, 2009 | Feb 5, 2009 | Yes |
| 00 | Mar 24, 2009 | — | — |
| 00 | Jan 12, 1984 | Apr 21, 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-219-33404 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-219-33404 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 56.7K
- bbl, last 12 reported months
- 3.94M
- bbl, all reported
- Feb 2026
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000043339 | H-1 Injection | Plugged Jul 10, 2006 | 1,000 | 2,250 | 4,500–5,100 |
| 000099976 | H-1 Injection | Active | 5,000 | 2,250 | 4,550–5,200 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 56,684 · prior 12 57,755(-2%)
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/21933404, documented in the API reference.