WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-439-30786

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-439-30786Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Nelson #1 HHZ42-439-31117Tarrant, TX · Enervest Operating L.L.C.0.68SURVEYS CASED HOLETIFF6,184 to 9,402Sep 12, 2008run May 7, 2005
Coburn #3HHZ42-439-31769Tarrant, TX · XTO Energy Inc.0.70Surveys Cased Hole3 TIFFMD FT 1:240 FT7,239 to 9,246Jun 9, 2008run Dec 1, 2006
Lake Country Estates East #1HHZ42-439-31118Tarrant, TX · Western Production Company0.81Neutron/Density PorosityTIFFLITHO-DENSITYU COMP. NEUTRON MIROLOG1,104 to 7,002Mar 14, 2008run Nov 2, 2005
Twin Mills Unit #2HHZ42-439-34827Tarrant, TX · Eagleridge Operating LLC0.91RESISTIVITYTIFF6,099 to 10,775May 20, 2013run Apr 30, 2010
Reed Mitchell Unit #a 5HHZ42-439-36400Tarrant, TX · Eagleridge Operating LLC0.99RESISTIVITYTIFF95 to 10,900Feb 5, 2013run Mar 28, 2012
Twin Mills Unit #1HHZ42-439-34826Tarrant, TX · Eagleridge Operating LLC0.99RESISTIVITYTIFF6,169 to 10,494Apr 15, 2013run Apr 13, 2010
Reed Mitchell Unit #b 3HHZ42-439-33067Tarrant, TX · Eagleridge Operating LLC1.08SURVEYS CASED HOLETIFF6,884 to 9,750Nov 2, 2011run Oct 21, 2008
Reed Mitchell Unit #a 2HHZ42-439-33153Tarrant, TX · Eagleridge Operating LLC1.12SURVEYS CASED HOLETIFF6,500 to 10,900Dec 12, 2011run Nov 8, 2008
Summers #1HZ42-439-31211Tarrant, TX · Trio Consulting & Management LLC1.15Resistivity2 TIFFHIGH RESOLUTI0N INDUCTION1,180 to 7,050Oct 6, 2006run May 15, 2005
Reed Mitchell Unit #a 3HHZ42-439-36398Tarrant, TX · Eagleridge Operating LLC1.19RESISTIVITYTIFF95 to 9,695Feb 25, 2013run Mar 16, 2012
Carter NE Unit #b 5HHZ42-439-34212Tarrant, TX · BKV North Texas LLC1.20SURVEYS CASED HOLETIFF5,000 to 9,808Dec 8, 2009run Apr 25, 2009
Carter NE Unit #b 17HHZ42-439-34511Tarrant, TX · BKV North Texas LLC1.22SURVEYS CASED HOLETIFF1,170 to 9,654Apr 29, 2010run Dec 20, 2009
Carter NE Unit #b 8HHZ42-439-32847Tarrant, TX · BKV North Texas LLC1.22SURVEYS CASED HOLETIFF5,120 to 10,000Oct 14, 2008run Jan 6, 2008
Carter SE Unit #b 22HHZ42-439-35723Tarrant, TX · BKV North Texas LLC1.25SURVEYS CASED HOLETIFF5,500 to 9,792Mar 13, 2012run May 29, 2011
Carter SE Unit #b 14HHZ42-439-34211Tarrant, TX · BKV North Texas LLC1.30SURVEYS CASED HOLETIFF5,000 to 9,730Nov 30, 2009run May 8, 2009
Carter NE Unit #b 4HHZ42-439-33391Tarrant, TX · BKV North Texas LLC1.31SURVEYS CASED HOLETIFF6,000 to 6,905Oct 9, 2009run Sep 7, 2008
Carter SE Unit #b 23HHZ42-439-35724Tarrant, TX · BKV North Texas LLC1.35SURVEYS CASED HOLETIFF5,500 to 9,886Mar 29, 2012run Jun 11, 2011
Hayco B Unit #1HHZ42-439-31236Tarrant, TX · XTO Energy Inc.1.49SURVEYS CASED HOLETIFF6,375 to 9,698Nov 6, 2009run Apr 22, 2006
Carter SE Unit #b 2HHZ42-439-34555Tarrant, TX · BKV North Texas LLC1.55SURVEYS CASED HOLETIFF5,500 to 9,733Jun 25, 2010run Dec 31, 2009
Reed Mitchell Unit #a 8HHZ42-439-36403Tarrant, TX · Eagleridge Operating LLC1.63RESISTIVITYTIFF94 to 11,604Feb 5, 2013run Jan 30, 2012
Reed Mitchell Unit #a 7HHZ42-439-36402Tarrant, TX · Eagleridge Operating LLC1.64RESISTIVITYTIFF90 to 11,517Feb 5, 2013run Feb 13, 2012
Reed Mitchell Unit #a 6HHZ42-439-36401Tarrant, TX · Eagleridge Operating LLC1.66RESISTIVITYTIFF90 to 10,110Feb 5, 2013run Feb 24, 2012
Carter SE Unit #b 3HHZ42-439-33247Tarrant, TX · BKV North Texas LLC1.66SURVEYS CASED HOLETIFF0 to 9,465Sep 11, 2009run Dec 10, 2008
Reed Mitchell Unit #a 4HHZ42-439-36399Tarrant, TX · Eagleridge Operating LLC1.69RESISTIVITYTIFF95 to 9,535Feb 5, 2013run Mar 6, 2012
Sloan a GU #1HZ42-439-31799Tarrant, TX · BKV Barnett LLC1.85RESISTIVITYTIFF1,302 to 6,343Jan 6, 2010run Nov 24, 2006
Hayco #d 3HHZ42-439-30666Tarrant, TX · XTO Energy Inc.1.85ResistivityTIFFARRAY INDUCTION SHALLOW FOCUSED ELECTRIC LOG TVD1,214 to 7,012Jun 9, 2008run Dec 8, 2004
Carter #b 12HHZ42-439-33494Tarrant, TX · BKV North Texas LLC1.89SURVEYS CASED HOLETIFF0 to 6,844Sep 29, 2009run Nov 26, 2008
Cranz #3HZ42-439-32678Tarrant, TX · BKV Barnett LLC1.91NEUTRON POROSITYTIFF1,315 to 6,463Dec 7, 2010run Nov 12, 2007
Carter #b 6HHZ42-439-31958Tarrant, TX · BKV North Texas LLC1.92SURVEYS CASED HOLETIFF5,224 to 9,735Sep 24, 2008run Apr 11, 2007
Edwards #142-439-30300Tarrant, TX · Vargas Energy Ltd.1.97ResistivityTIFFARRAY INDUCTION IMAGER GAMMA RAY SP1,134 to 7,228Dec 13, 2006run Oct 30, 2002
Carter #b 11HHZ42-439-35691Tarrant, TX · BKV North Texas LLC1.98SURVEYS CASED HOLETIFF5,670 to 9,970Apr 3, 2012run Apr 22, 2011

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.