TEXAS · WELLS · MIDLAND COUNTY · FEE "AT" LEASE · API 42-329-36034 · DISTRICT 7B
Fee At #1
Midland County · Spraberry (Trend Area) field · Producing · Vertical
- Fields on the latest permit · any of 2
- Lowe, West (Strawn) · Spraberry (Trend Area)
- Not one formation; the well must be completed in one of them, and no target formation is stated.
Fee At #1 (API 42-329-36034) is a well in Midland County operated by Fasken Oil And Ranch Ltd., completed April 9, 2010 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit (amended once), issued August 2, 2008, permitted to 10,845 ft.
Completion filings report 5 formation tops, including Clear Fork, Spraberry, Dean, Wolfcamp.
Its lease has reported 1.32M barrels of oil and 3.39M mcf of gas since September 2009, last reporting volume in August 2026. The lease carries 18 wells, so these are lease totals, not this well alone.
Operator of record
- Based in
- Midland, TX
- P-5 status
- Active (A)
- P-5 last filed
- Nov 14, 2025
- Permits on file
- 2,059
- Phone
- (432) 687-1777
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Fasken Oil and Ranch Ltd. |
| Production reports | Fasken Oil and Ranch, Ltd.through Aug 2026 |
| Latest permit | Fasken Oil and Ranch, Ltd.Aug 2, 2008 |
- 10,845
- total depth, ft
- 2
- permits on file
- Aug 2, 2008
- last permit issued
- Apr 9, 2010
- completed
- 1.32M
- cumulative oil, bbl
- 3.39M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · SEP 2009 THROUGH AUG 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Apr 9, 2010
- 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.
Wells nearby
Every well with a location on file around this well, in any state, nearest first.
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
Lease production
PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026
Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 18 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Fee "At" O-10-39599 | Spraberry (Trend Area) | Fasken Oil and Ranch, Ltd. | 18 | 1.32M | 3.39M | Sep 2009 – Aug 2026 |
Oil, barrels lease total
Last 12 months 48,524 · prior 12 41,742(+16%)
Gas, mcf lease total
Last 12 months 91,984 · prior 12 68,952(+33%)
Wells named Fee At
Fasken Oil and Ranch Ltd.'s other wells filed under this lease name in Midland County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.
Loading the lease's wellsChain of custody
Every operator that reported production on this well's lease, in order.
- 1Fasken Oil and Ranch, Ltd.Sep 2009 → Aug 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 666676-98 | Drill | Fasken Oil and Ranch, Ltd. | Jun 11, 2015 | Aug 2, 2008 | Feb 23, 2010 | 11,100 |
| 666676-99 | Drill | Fasken Oil and Ranch, Ltd. | Jul 14, 2008 | Aug 2, 2008 | Feb 23, 2010 | 11,100 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Apr 9, 2010 | Fee At O-10-39599 | Spraberry (Trend Area) | Fasken Oil and Ranch Ltd. | Producing | 10,845 |
Formation tops
As filed on W-2/G-1. Subsea from 2,853 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Clear ForkLOWER CLEARFORK | 7,140 | -4,287 |
| SpraberryUPPER SPRABERRY | 8,081 | -5,228 |
| Dean | 9,378 | -6,525 |
| Wolfcamp | 9,576 | -6,723 |
| Strawn | 10,660 | -7,807 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,670 | 10,520 | Perforated |
| 10,740 | 10,760 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 480 | 13.5 | 250 S |
| 5.5 | 10,838 | 7.875 | 1,000 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 | Jun 16, 2015 | May 12, 2010 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Jul 6, 2015. 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 POROSITY | TIFF | 6500 to 1785 as filed | Jul 6, 2015run Mar 19, 2010 | 2.35 |
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-329-36034 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-329-36034 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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/32936034, documented in the API reference.