TEXAS · WELLS · UPTON COUNTY · LOIS LEASE · API 42-461-34994 · DISTRICT 6E
Lois #1108
Upton County · Spraberry (Trend Area) field · Shut In · Vertical
Lois #1108 (API 42-461-34994) is a well in Upton County operated by Firebird Energy II LLC, completed April 27, 2006 and listed as shut in on the RRC schedule, shut in August 1, 2026.
The RRC has issued one drilling permit, issued December 30, 2005, permitted to 10,600 ft.
It was permitted by Henry Petroleum LP and has since transferred to Firebird Energy II LLC on the wellbore schedule.
Completion filings report 3 formation tops, including T. Spraberry, T. Dean, T. Wolfcamp.
Its lease has reported 147K barrels of oil and 596K mcf of gas since April 2006, last reporting volume in November 2025. The lease carries 3 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Henry Petroleum LP; the EWA schedule now lists a different operator.
- Based in
- Fort Worth, TX
- P-5 status
- Active (A)
- P-5 last filed
- Aug 12, 2024
- Permits on file
- 272
- Phone
- (817) 857-7800
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Firebird Energy II LLC |
| Production reports | Firebird Energy II LLCthrough Nov 2025 |
| Latest permit | Henry Petroleum LPDec 30, 2005 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 10,600
- total depth, ft
- 1
- permits on file
- Dec 30, 2005
- last permit issued
- Apr 27, 2006
- completed
- 147K
- cumulative oil, bbl
- 596K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2006 THROUGH Nov 2025
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Apr 27, 2006
- Shut in
- Aug 1, 2026
- 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 3 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Lois O-9-15939 | Spraberry (Trend Area) | Firebird Energy II LLC | 3 | 147K | 596K | Apr 2006 – Nov 2025 |
Oil, barrels lease total
Last 12 months 721 · prior 12 68
Gas, mcf lease total
Last 12 months 2,250 · prior 12 226
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Henry Petroleum LPApr 2006 → Apr 2007
- 2Summit Petroleum LLCMay 2007 → May 2023
- 3Firebird Energy II LLCSep 2024 → Oct 2025
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 611602-99 | Drill | Henry Petroleum LP | Dec 27, 2005 | Dec 30, 2005 | Jan 28, 2006 | 10,800 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Apr 27, 2006 | Lois O-9-15939 | Spraberry (Trend Area) | Firebird Energy II LLC | Shut In · shut in Aug 1, 2026 | 10,600 |
Formation tops
As filed on W-2/G-1. Subsea from 2,871 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| T. Spraberry | 7,775 | -4,904 |
| T. Dean | 8,985 | -6,114 |
| T. Wolfcamp | 9,140 | -6,269 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,970 | 10,530 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 508 | 12.25 | 325 S |
| 5.5 | 10,600 | 7.875 | 1,050 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 | May 14, 2007 | Mar 9, 2007 | — |
| 00 | Sep 29, 2006 | May 24, 2006 | Yes |
| 00 | Jun 9, 2006 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Feb 20, 2009. Neutron. 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 |
|---|---|---|---|---|
| NEUTRON POROSITYSpans T. Spraberry, T. Dean, T. Wolfcamp | TIFF | 4,000 to 10,571 | Feb 20, 2009run Feb 20, 2006 | 2.66 |
"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-461-34994 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-461-34994 → 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/46134994, documented in the API reference.