WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-461-00712

Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof API 42-461-00712Clear

Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.

20 LOG FILES ON 19 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Allison #251542-461-39069Upton, TX · Summit Petroleum LLC0.54NeutronTIFF0 to 10,598Oct 27, 2017
Allison #250342-461-39068Upton, TX · Summit Petroleum LLC0.67NEUTRON POROSITYTIFF0 to 10,529Feb 17, 2017run Feb 27, 2014
Allison #250742-461-39063Upton, TX · Summit Petroleum LLC0.76NEUTRON POROSITYTIFF0 to 10,558Feb 22, 2017run Feb 4, 2014
Allison #251642-461-39058Upton, TX · Summit Petroleum LLC1.07NEUTRON POROSITYTIFF0 to 10,283Feb 22, 2017run Dec 23, 2013
Allison #250642-461-39062Upton, TX · Summit Petroleum LLC1.08NEUTRON POROSITYTIFF0 to 10,284Feb 22, 2017run Jan 1, 2014
Allison #250442-461-38871Upton, TX · Summit Petroleum LLC1.10NEUTRON POROSITYTIFF0 to 10,500Nov 23, 2016run Dec 4, 2013
Allison #251342-461-38870Upton, TX · Summit Petroleum LLC1.27NEUTRON POROSITYTIFF0 to 10,527Nov 23, 2016run Nov 11, 2013
Allison #251042-461-39061Upton, TX · Summit Petroleum LLC1.28NEUTRON POROSITYTIFF0 to 10,569Feb 1, 2017run Jan 16, 2014
Allison #250842-461-38852Upton, TX · Summit Petroleum LLC1.31NEUTRON POROSITYTIFF0 to 10,412Sep 21, 2016run Sep 23, 2013
Kayla #221542-461-39824Upton, TX · Summit Petroleum LLC1.48NeutronTIFF3,000 to 10,408Feb 13, 2018
Dolores #1542-461-37058Upton, TX · Firebird Energy II LLC1.49NEUTRON POROSITYTIFF4,000 to 10,861Jan 16, 2014run Feb 4, 2011
Kayla #220342-461-39181Upton, TX · Summit Petroleum LLC1.59NeutronTIFF4,000 to 10,433Sep 11, 2018
Kelly #342-461-35197Upton, TX · Summit Petroleum LLC1.61NEUTRON POROSITYTIFF5,500 to 9,990Aug 27, 2008run Feb 1, 2007
Dolores #1142-461-37935Upton, TX · Firebird Energy II LLC1.63NEUTRON POROSITYTIFF4,000 to 10,821May 18, 2015run May 28, 2012
Lora Lynn #1642-461-36496Upton, TX · Firebird Energy II LLC1.68NEUTRON POROSITYTIFF3,000 to 10,654Feb 25, 2013run Feb 4, 2010
Lora Lynn #1242-461-37034Upton, TX · Firebird Energy II LLC1.72NEUTRON POROSITYTIFF4,000 to 10,916Dec 9, 2013run Jan 8, 2011
Kayla #220742-461-39660Upton, TX · Summit Petroleum LLC1.80NeutronLAS + TIFF0 to 10,430Sep 12, 2017
Kelly #442-461-35198Upton, TX · Summit Petroleum LLC1.81NEUTRON POROSITYTIFF5,900 to 9,940Jun 21, 2010run Jun 22, 2007
Kayla #221142-461-39825Upton, TX · Summit Petroleum LLC1.87NeutronTIFF15 to 10,452Feb 13, 2018

About this data

Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. 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. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.

Developers: this page as JSON is GET /v1/data/logs, documented in the API reference.