TEXAS · WELLS · UPTON COUNTY · MAYDEAN136 LEASE · API 42-461-37209 · DISTRICT 6E
MAYDEAN136 #10
Upton County · Spraberry (Trend Area) field · Producing · Vertical
- Fields on the latest permit · any of 3
- King Mountain, N. (Bend) · King Mountain, N.(strawn) · Spraberry (Trend Area)
- Not one formation; the well must be completed in one of them, and no target formation is stated.
Maydean136 #10 (API 42-461-37209) is a well in Upton County operated by Firebird Energy II LLC, completed June 25, 2011 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued February 11, 2011, permitted to 11,190 ft.
It was permitted by Cog Operating LLC and has since transferred to Firebird Energy II LLC on the wellbore schedule.
Completion filings report 5 formation tops, including Clear Fork, Spraberry, Wolfcamp, Strawn.
Its lease has reported 71.5K barrels of oil and 481K mcf of gas since April 2008, last reporting volume in April 2026. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by COG Operating LLC; 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 Apr 2026 |
| Latest permit | COG Operating LLCFeb 11, 2011 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 11,190
- total depth, ft
- 1
- permits on file
- Feb 11, 2011
- last permit issued
- Jun 25, 2011
- completed
- 71.5K
- cumulative oil, bbl
- 481K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Apr 2008 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jun 25, 2011
- 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 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| MAYDEAN136 O-9-16564 | Spraberry (Trend Area) | Firebird Energy II LLC | 2 | 71.5K | 481K | Apr 2008 – Apr 2026 |
Gas, mcf lease total
Last 12 months 5,823 · prior 12 4,305(+35%)
Oil, barrels lease total
Last 12 months 487 · prior 12 228(+114%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Henry Petroleum LPApr 2008 → Dec 2008
- 2COG Operating LLCJan 2009 → Aug 2024
- 3Firebird Energy II LLCOct 2024 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 710023-99 | Drill | COG Operating LLC | Feb 9, 2011 | Feb 11, 2011 | Apr 1, 2011 | 12,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jun 25, 2011 | MAYDEAN136 O-9-16564 | Spraberry (Trend Area) | Firebird Energy II LLC | Producing | 11,190 |
Formation tops
As filed on W-2/G-1. Subsea from 2,794 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 6,660 | 10,890 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 827 | 12.25 | 430 S |
| 5.5 | 11,190 | 7.875 | 885 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 | Oct 24, 2012 | Jul 7, 2011 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Apr 7, 2014. 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 Clear Fork, Spraberry, Wolfcamp, Strawn, Bend | TIFF | 4,000 to 11,132 | Apr 7, 2014run May 5, 2011 | 9.19 |
"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-37209 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-461-37209 → 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/46137209, documented in the API reference.