TEXAS · WELLS · UPTON COUNTY · DAVIDSON "F" LEASE · API 42-461-35008 · DISTRICT 6E
Davidson F #202
Upton County · Spraberry (Trend Area) field · Producing · Vertical
Davidson F #202 (API 42-461-35008) is a well in Upton County operated by Diamondback E&P LLC, completed September 28, 2006 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued January 23, 2006, permitted to 10,410 ft.
It was permitted by Lcx Energy, LLC and has since transferred to Diamondback E&P LLC on the wellbore schedule.
Completion filings report 5 formation tops, including Yates, San Andres, Spraberry, Dean.
Its lease has reported 546K barrels of oil and 1.44M mcf of gas since September 2006, last reporting volume in April 2026. The lease carries 4 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by LCX Energy, LLC; the EWA schedule now lists a different operator.
- Based in
- Midland, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- May 4, 2026
- Permits on file
- 5,243
- Phone
- (432) 221-7400
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Diamondback E&P LLC |
| Production reports | Diamondback E&P LLCthrough Apr 2026 |
| Latest permit | LCX Energy, LLCJan 23, 2006 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 10,410
- total depth, ft
- 1
- permits on file
- Jan 23, 2006
- last permit issued
- Sep 28, 2006
- completed
- 546K
- cumulative oil, bbl
- 1.44M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Sep 2006 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Sep 28, 2006
- 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 4 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Davidson "F" O-9-16060 | Spraberry (Trend Area) | Diamondback E&P LLC | 4 | 546K | 1.44M | Sep 2006 – Apr 2026 |
Oil, barrels lease total
Last 12 months 4,182 · prior 12 3,481(+20%)
Gas, mcf lease total
Last 12 months 6,193 · prior 12 3,446(+80%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1LCX Energy, LLCSep 2006 → Sep 2009
- 2Endeavor Energy Resources L.P.Oct 2009 → Dec 2024
- 3Diamondback E&P LLCJan 2025 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 612705-99 | Drill | LCX Energy, LLC | Jan 19, 2006 | Jan 23, 2006 | Jun 24, 2006 | 11,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Sep 28, 2006 | Davidson F O-9-16060 | Spraberry (Trend Area) | Diamondback E&P LLC | Producing | 10,410 |
Formation tops
As filed on W-2/G-1. Subsea from 2,821 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Yates | 2,725 | 96 |
| San Andres | 5,125 | -2,304 |
| Spraberry | 7,750 | -4,929 |
| Dean | 8,975 | -6,154 |
| Wolfcamp | 9,375 | -6,554 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,746 | 10,304 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 432 | 12.25 | 200 S |
| 5.5 | 10,407 | 7.875 | 1,375 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 | Mar 7, 2007 | Nov 2, 2006 | Yes |
| 00 | Nov 13, 2006 | — | — |
Well logs
1 log loaded from the RRC's log index, the latest received Jul 24, 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 San Andres, Spraberry, Dean, Wolfcamp | TIFF | 7,000 to 10,333 | Jul 24, 2009run Aug 15, 2006 | 4.40 |
"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-35008 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-461-35008 → 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/46135008, documented in the API reference.