TEXAS · WELLS · DAWSON COUNTY · OVMLC LEASE · API 42-115-33602 · DISTRICT 7B
Ovmlc #1
Dawson County · Spraberry (Trend Area) field · Producing · Vertical
Ovmlc #1 (API 42-115-33602) is a well in Dawson County operated by Diamondback E&P LLC, completed October 25, 2013 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued July 29, 2013, permitted to 10,379 ft.
It was permitted by Crownquest Operating, LLC and has since transferred to Diamondback E&P LLC on the wellbore schedule.
Completion filings report 4 formation tops, including Spraberry, Strawn, Atoka, Mississippian.
Its lease has reported 141K barrels of oil and 224K mcf of gas since October 2013, 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 Crownquest Operating, 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 | Crownquest Operating, LLCJul 29, 2013 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 10,379
- total depth, ft
- 1
- permits on file
- Jul 29, 2013
- last permit issued
- Oct 25, 2013
- completed
- 141K
- cumulative oil, bbl
- 224K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Nov 2013 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Oct 25, 2013
- 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 |
|---|---|---|---|---|---|---|
| Ovmlc O-10-44757 | Spraberry (Trend Area) | Diamondback E&P LLC | 2 | 141K | 224K | Oct 2013 – Apr 2026 |
Oil, barrels lease total
Last 12 months 3,607 · prior 12 4,073(-11%)
Gas, mcf lease total
Last 12 months 1,779 · prior 12 1,702(+5%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Crownquest Operating, LLCNov 2013 → May 2024
- 2Endeavor Energy Resources L.P.Jun 2024 → Dec 2024
- 3Diamondback E&P LLCJan 2025 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 764346-99 | Drill | Crownquest Operating, LLC | Jun 10, 2013 | Jul 29, 2013 | Sep 5, 2013 | 12,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Oct 25, 2013 | Ovmlc O-10-44757 | Spraberry (Trend Area) | Diamondback E&P LLC | Producing | 10,379 |
Formation tops
As filed on W-2/G-1. Subsea from 2,799 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Spraberry | 7,701 | -4,902 |
| Strawn | 9,875 | -7,076 |
| Atoka | 10,071 | -7,272 |
| Mississippian | 10,134 | -7,335 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,701 | 10,226 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 292 | 17.5 | 400 S |
| 8.625 | 4,587 | 11 | 1,050 S |
| 5.5 | 10,351 | 7.875 | 1,850 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 | Jul 14, 2014 | Feb 20, 2014 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Sep 4, 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 Spraberry, Strawn, Atoka, Mississippian | TIFF | 4,300 to 10,301 | Sep 4, 2014run Oct 8, 2013 | 5.15 |
"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-115-33602 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-115-33602 → 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/11533602, documented in the API reference.