WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-499-00549

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-499-00549Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Brogdon #142-499-32047Wood, TX · Goldston Oil Corporation0.91Combination: Resistivity/Neutron Density PorosityTIFFPLATFORM EXPRESS937 to 4,165Nov 16, 2006run Apr 3, 2006
Blackwell C C #142-499-32060Wood, TX · Southwest Operating Inc.-Tyler0.98RESISTIVITYTIFF826 to 9,506Dec 18, 2009run Sep 19, 2006
Rock Hill #142-499-32111Wood, TX · Dominus Energy Inc1.09RESISTIVITYTIFF851 to 10,088Apr 5, 2013run Nov 9, 2011
R. L. Lipscomb et al #342-499-32037Wood, TX · Goldston Oil Corporation1.32RESISTIVITYTIFF950 to 7,479Jun 23, 2011run Sep 19, 2005
Baylor University Unit #142-499-32096Wood, TX · Southwest Operating Inc.-Tyler1.40COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF784 to 9,514Feb 6, 2013run Jan 17, 2010
Raley #1__42-499-32056Wood, TX · Goldston Oil Corporation1.49Combination: Resistivity/Neutron Density PorosityTIFFPLATFORM EXPRESS982 to 6,545Oct 17, 2006run Aug 7, 2006
Lloyd Unit #142-499-32090Wood, TX · Southwest Operating Inc.-Tyler1.54COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF849 to 9,515Aug 20, 2012run Jan 14, 2009
Lipscomb #1__42-499-32098Wood, TX · Barrow-Shaver Resources Co.1.56ACOUSTIC POROSITYTIFF980 to 8,502Dec 17, 2010run Jun 12, 2010
Noe H. H. #342-499-32142Wood, TX · Southwest Operating Inc.-Tyler1.62RESISTIVITYTIFF3,649 to 4,649Apr 10, 2017run Apr 14, 2014
Pittman Maude #242-499-32122Wood, TX · Southwest Operating Inc.-Tyler1.64COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF814 to 4,350Aug 25, 2015run Aug 16, 2012
Noe H. H. #242-499-32127Wood, TX · Southwest Operating Inc.-Tyler1.69RESISTIVITYTIFF806 to 4,353Nov 2, 2015run Oct 30, 2012
Clay Jerry H. #142-499-32103Wood, TX · Southwest Operating Inc.-Tyler1.71RESISTIVITYTIFF6,400 to 9,510Feb 3, 2014run Nov 19, 2010
Clay Jerry H. #142-499-32103Wood, TX · Southwest Operating Inc.-Tyler1.71RESISTIVITYTIFF6,400 to 9,510Sep 3, 2015run Nov 19, 2010
Clay Jerry H. #242-499-32130Wood, TX · Southwest Operating Inc.-Tyler1.77RESISTIVITYTIFF33262 to 4362 as filedFeb 8, 2016run Nov 24, 2012
Brogdon Heirs #1__42-499-32144Wood, TX · White Rock Exploration Inc.1.86RESISTIVITYTIFF937 to 6,874Nov 24, 2015run Aug 16, 2014
Cantrell E. #142-499-32123Wood, TX · TTK Energy LLC1.92InductionTIFF802 to 10,701Jan 30, 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.